-
Notifications
You must be signed in to change notification settings - Fork 193
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
Add region property for CloudBuildTrigger Resource #672
Comments
Hi @travisrandolph-bestbuy, would you mind providing a link to the REST API documentation you're looking at? I checked https://cloud.google.com/build/docs/api/reference/rest/v1/projects.triggers and couldn't find any mention of a |
@mbzomowski after digging into this further I think this is the API being used. There you can see location in the trigger name. |
@travisrandolph-bestbuy, thank you for the request! Since your request is to support a new feature in one of our Terraform-based resources, Note that timelines for Terraform resource requests can be pretty unpredictable. We recommend making the contribution yourself if possible (which we would also highly appreciate!). If you have other concerns or would like to escalate this request, please feel free to reach out to GCP support. |
@caieo it looks like this issue was created to add support for location. It looks like the pull request with the change was just merged. |
@travisrandolph-bestbuy after they create a release with that change we'll upgrade our TF provider, and do a Config Connector release the week after that. Should be about 4 weeks FYI. |
|
Checklist
Describe the feature or resource
The Cloud Build trigger API now supports region. We'd like to have this option for our KCC resources.
Additional information
No response
Importance
This isn't a blocker, but currently our triggers and history pages don't match up. This is due to the fact that we are using custom worker pools that are in another region. If KCC supports the region property for CloudBuildTriggers we can change the region to match.
The text was updated successfully, but these errors were encountered: