-
Notifications
You must be signed in to change notification settings - Fork 910
New issue
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
Errors when attempting to use GCS volumes in cloud-run-v2 #2684
Comments
This looks like a bug, let me take a look at it. |
Should it be using each.key and each.value rather than volumes.key and volumes.value? #noob |
wiktorn
added a commit
that referenced
this issue
Nov 14, 2024
4 tasks
Close :-) |
wiktorn
added a commit
that referenced
this issue
Nov 14, 2024
Cool! Will try that in the morning. |
wiktorn
added a commit
that referenced
this issue
Nov 14, 2024
wiktorn
added a commit
that referenced
this issue
Nov 14, 2024
The fix (mostly) worked for me. Needed to add |
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Cannot use the new support for GCS volumes in cloud-run-v2. Is it broken, or am I doing it wrong?
It was added:
#2638
Environment
To Reproduce
Steps to reproduce the behavior
Add a "volumes" stanza to a cloud-run-v2 module-resource in terraform:
Expected behavior
A clear and concise description of what you expected to happen.
Cloudrun to be created with this volume.
It works fine with the underlying provider:
So problem seems to be in service.tf https://github.com/GoogleCloudPlatform/cloud-foundation-fabric/blob/master/modules/cloud-run-v2/service.tf#L208 which may be generating incorrect dynamic content?? I don't know how to debug this.
Result
Terraform output and/or error messages
The text was updated successfully, but these errors were encountered: