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
Terraform currently supports S3 as a Module Source. We only use GCP so want to be able to use GCS as a Module Source
Attempted Solutions
A workaround I am currently using is to use Google Storage Interoperability. This provides AWS keys used for API calls to a S3 like protocol. Doing this I:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Jul 25, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Current Terraform Version
Use-cases
Terraform currently supports S3 as a Module Source. We only use GCP so want to be able to use GCS as a Module Source
Attempted Solutions
A workaround I am currently using is to use Google Storage Interoperability. This provides AWS keys used for API calls to a S3 like protocol. Doing this I:
Proposal
Ideally this solution should work as such:
source = "gcs::https://storage.googleapis.com/modules-bucket/awesome-module.tar.gz"
References
None
The text was updated successfully, but these errors were encountered: