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
I'm actually using dekorate via Quarkus Kubernetes extension.
The generated env in a deployment is shuffled every time the yaml is regenerated. This causes a problem since the manifest is not idempotent.
This is the issue on Quarkus: quarkusio/quarkus#39167
Would it be possibile to preserve the ordering?
The text was updated successfully, but these errors were encountered:
I'm looking into it, but having some difficulty trying to implement this in dekorate.
Any hint about where to put this logic?
Sorry, something went wrong.
No branches or pull requests
I'm actually using dekorate via Quarkus Kubernetes extension.
The generated env in a deployment is shuffled every time the yaml is regenerated. This causes a problem since the manifest is not idempotent.
This is the issue on Quarkus: quarkusio/quarkus#39167
Would it be possibile to preserve the ordering?
The text was updated successfully, but these errors were encountered: