-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
google_artifact_registry_repository location appears to be required #10436
google_artifact_registry_repository location appears to be required #10436
Comments
I can confirm that addintg |
This seems to be bug caused from
location to provider region when location is not passed, and thus, the location ends up being empty string.
In such case the path used for the API call is
(notice I'll see whether I manage to fix it and create pull request for it |
Encountered the Same behaviour, adding the |
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. |
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
Terraform v1.0.5
on linux_amd64
Affected Resource(s)
Terraform Configuration Files
Output
Expected Behavior
The repository is created with the location inherited from the provider region, as the
location
argument is documented as optional.Actual Behavior
The repository is not created because GCP rejects the request due to an invalid argument, as the location argument is required and not necessarily equivalent to any region.
Steps to Reproduce
This issue was reported in #10184. I confirmed that the workaround of adding the
location
argument solved the problem.References
b/272798286
The text was updated successfully, but these errors were encountered: