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
As the GCP instance reads the metadata on the fly for parameters, the credentials and keys are exposed in console if we use this registry.
The text was updated successfully, but these errors were encountered:
+1 to this. Could this module not allow users to pull the secrets from a GCS bucket with a client side KMS key which only the primary/secondary service account has access to? Or give the option to point to a Vault instance which would pull this data at boot time. It seems this issue also exists on the AWS installation module, where secrets are stored in User Data: https://github.com/hashicorp/terraform-aws-terraform-enterprise/blob/87a10c9893e71261404fe70a80ee4e4cd8f22fca/config.tf#L22
Sorry, something went wrong.
No branches or pull requests
As the GCP instance reads the metadata on the fly for parameters, the credentials and keys are exposed in console if we use this registry.
The text was updated successfully, but these errors were encountered: