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

Clean up the README to remove old "conjurize" references #97

Closed
2 tasks
izgeri opened this issue Jul 2, 2020 · 3 comments
Closed
2 tasks

Clean up the README to remove old "conjurize" references #97

izgeri opened this issue Jul 2, 2020 · 3 comments

Comments

@izgeri
Copy link
Contributor

izgeri commented Jul 2, 2020

AC:

@izgeri
Copy link
Contributor Author

izgeri commented Jul 2, 2020

@alexkalish can you please confirm that removing the reference to conjurize is ok here? the alternative is adding a big Conjur Enterprise v4 only caveat to this section and then removing it when we deprecate v4 support

I'd also appreciate your feedback on whether the next tag can announce deprecation for Conjur v4 support, to be removed in a soon-to-be-tagged future version.

@izgeri izgeri self-assigned this Jul 7, 2020
@izgeri izgeri mentioned this issue Jul 7, 2020
6 tasks
@sgnn7 sgnn7 closed this as completed Jul 8, 2020
@alexkalish
Copy link
Contributor

@sgnn7, @izgeri: Looks like the 🚢 may have already sailed, but I think that we should just put this identity method behind a big "v4 ONLY" stipulation. We aren't removing this feature from v4; we just are not supporting it moving forward.

Regarding v4, our plan is to not support this version with Puppet module v3. So are you asking if we can declare that deprecation now?

@izgeri
Copy link
Contributor Author

izgeri commented Jul 8, 2020

@alexkalish it's not hard to add it back with the big caveat; I can do that now, with plans to remove it when we actually deprecate v4

and yes, I'd like to announce the deprecation in the next tag if we can, to be actually removed in the following version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants