-
Notifications
You must be signed in to change notification settings - Fork 307
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
Push to instrumenta on release or create deprecation plan #419
Comments
I am in favor of deprecation as well. If we start sharing now that it will be deprecated, we can ensure people have time to update before the next release. The open question for me is what channels we should use to share. We can leave a note on conftest.dev and on the OPA slack and hopefully that is enough notice. |
I feel as long as the DockerHub README had a blurb about the migration (e.g. https://hub.docker.com/_/opensuse), and we made a note of it in the 0.22.0 release notes on GitHub, that would cover enough for users to be able to easily find the new image. FWIW there doesn't appear to be a paved path for this docker/hub-feedback#907 |
Updated our |
PR #411 updated the Circle config to push on release, but did not include the
instrumenta
project.From @garethr's comment in #417 (comment), an announcement should be put together stating its official deprecation.
To resolve this, the Circle config should be updated to also push to
instrumenta
or formally announce thatinstrumenta
is deprecated in favor of the openpolicyagent org (this gets my vote).@garethr @Blokje5
The text was updated successfully, but these errors were encountered: