Open antoniomacri opened 1 month ago
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: https://github.com/quarkusio/quarkus/issues/39167
Would it be possibile to preserve the ordering?
I'm looking into it, but having some difficulty trying to implement this in dekorate.
Any hint about where to put this logic?
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: https://github.com/quarkusio/quarkus/issues/39167
Would it be possibile to preserve the ordering?