We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, AKO by default adds some markers to some objects it creates, such as
While useful in their own right, being able to add some custom information here, would allow me to pass some info to other automation.
Adding a parameter to either the HostRule or HTTPRule CR, accepting a map of custom markers.
HostRule
HTTPRule
Also, it may be worthwhile to have the ability to add "global" custom markers (possibly as values in the AKO helm chart)
Being able to pass in custom markers, can allow me to use them in custom controlscripts when/if necessary.
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem? Please describe.
Currently, AKO by default adds some markers to some objects it creates, such as
While useful in their own right, being able to add some custom information here, would allow me to pass some info to other automation.
Describe the solution you'd like
Adding a parameter to either the
HostRule
orHTTPRule
CR, accepting a map of custom markers.Also, it may be worthwhile to have the ability to add "global" custom markers (possibly as values in the AKO helm chart)
Being able to pass in custom markers, can allow me to use them in custom controlscripts when/if necessary.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: