feat(asm): Adding CA option without providing CA_CERT maps and adding revision_name flag #952
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
This is to align the tf module with the install_asm script as used for Citadel to MeshCA in the official documentation: https://cloud.google.com/service-mesh/docs/ca-migration
It adds the --revision_name flag, so we can deploy a second ASM control plane of the same ASM version using a unique revision name.
It also lets you deploy ASM without specifying the maps for --ca_certs. If you only specify, --ca citadel, it will now deploy successfully.