You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the script generates and installs ASM config, which is not suitable for GitOps integration. Ideally, users should treat their config as code, and review a diff of all changes before deploying to production via GitOps. I think all that is needed here is a way to dump the config to stdout instead of applying it directly.
The text was updated successfully, but these errors were encountered:
I was thinking about this and realized this might not have been what you wanted. The PR prints the config from this repo as-is, i.e. without passing it through istioctl manifest generate. Is that your intent and/or do you know whether people would prefer dry or hydrated configs at this step in the pipeline?
Currently, the script generates and installs ASM config, which is not suitable for GitOps integration. Ideally, users should treat their config as code, and review a diff of all changes before deploying to production via GitOps. I think all that is needed here is a way to dump the config to stdout instead of applying it directly.
The text was updated successfully, but these errors were encountered: