Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update CyberArk Conjur Secrets Lookup branding #13119

Closed
5 of 9 tasks
infamousjoeg opened this issue Oct 26, 2022 · 0 comments · Fixed by #13121
Closed
5 of 9 tasks

Update CyberArk Conjur Secrets Lookup branding #13119

infamousjoeg opened this issue Oct 26, 2022 · 0 comments · Fixed by #13121

Comments

@infamousjoeg
Copy link
Contributor

Please confirm the following

  • I agree to follow this project's code of conduct.
  • I have checked the current issues for duplicates.
  • I understand that AWX is open source software provided for free and that I might not receive a timely response.

Bug Summary

Current name for Conjur's external Secrets Management System lookup is CyberArk Conjur Secrets Lookup. The name should be updated to match branding CyberArk Conjur Secrets Manager Lookup.

AWX version

21.7.0

Select the relevant components

  • UI
  • API
  • Docs
  • Collection
  • CLI
  • Other

Installation method

docker development environment

Modifications

no

Ansible version

2.13.5

Operating system

Ubuntu 22.04.1 LTS

Web browser

No response

Steps to reproduce

This is not relevant. Look at the current Lookup name in Credentials.

Expected results

The lookup name should match current CyberArk branding.

Actual results

It does not.

Additional information

PR already prepared and will be submitted shortly.

infamousjoeg added a commit to infamousjoeg/awx that referenced this issue Oct 26, 2022
TheRealHaoLiu pushed a commit that referenced this issue Nov 10, 2022
* Fixes #13119 #13120 Cloud support & update brand

* rm base64 import to pass lint

* Update references across the board

* Removed final reference to CyberArk Conjur Secret Lookup
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants