-
Notifications
You must be signed in to change notification settings - Fork 2
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
Migrate this Ansible role to the Conjur Ansible collection #30
Comments
@BradleyBoutcher This could likely be a handful of cards, so please split it out once you have a complete plan:
|
@BradleyBoutcher fyi the docs card just got moved to cyberark/conjur-docs#1015. I added it to the epic. |
We should take the following steps to deprecate this project:
|
I'd like to get @alexkalish's take on (5), e.g. what the right way to announce deprecation is. do we need a new tag? can we just update the README to indicate that if you are using Ansible v2.9+, we recommend using the collection instead (with a link)? do we need to add |
@izgeri: I'm not sure that I have a strong opinion. I do know that users should be clearly informed of the following:
Readme is probably fine, assuming that is primary place where the component is consumed. |
Thanks @alexkalish. I'm going to copy this convo into #42, which is the issue for deprecating this standalone role. This issue is the one for migrating the role to the collection, for which there is an open PR at cyberark/ansible-conjur-collection#38. |
AC:
The text was updated successfully, but these errors were encountered: