-
Notifications
You must be signed in to change notification settings - Fork 68
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
Be able to create/update/delete operator policies #202
Comments
Pausing this work for now. |
This issue has been marked as stale due to 60 days of inactivity. Stale issues will be closed after a further 30 days of inactivity; please remove the stale label in order to prevent this occurring. |
Topology Operator does not support Operator Policies at the moment. We can continue this work. |
This issue has been marked as stale due to 60 days of inactivity. Stale issues will be closed after a further 30 days of inactivity; please remove the stale label in order to prevent this occurring. |
Closing stale issue due to further inactivity. |
Is this still considered to be implemeted in future releases? Support for operator policies would be great.. |
We don't have bandwidth to work on this feature. A PR would be welcome 🙏 |
* Bump Golang Use Golang 1.21 locally on the dev machine and bump Golang to 1.21 in Dockerfile make manifests * Support RabbitMQ operator policies Closes #202 * Add workaround for Go 1.21 since codeql does not (yet) support Go 1.21, see github/codeql-action#1842 * Fix test flake * Add missing test * Apply feedback
Is your feature request related to a problem? Please describe.
Be able to create/update/delete operator policies.
Using rabbithole support: https://github.com/michaelklishin/rabbit-hole/blob/master/operator_policies.go
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: