-
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
Add support for Cloud Run v2 jobs #1954
Conversation
8fbf94e
to
030f02e
Compare
I'll add more E2E tests, as we have fixtures. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job! (no pun intended :)
I have reviewed the CR module so far, probably others are more skilled to review the rest.
* create a separate file for service creation (service.tf) and job (job.tf) - for easy comparison * add E2E tests where possibile * remove default value for input variable `region` * fix subnet range VPC Access Connector example * add creation of service account for audit logs call (trigger requires service account) * use provided trigger service account email in `local.trigger_sa_email`, so explicitly provided SA is passed to trigger * set default value for vpc_connector_create.throughput.max, to match what is set by GCP API, as provider uses wrong default of 300 which results in perma-diff * create inventory fiels for all examples
Global changes * (tests) add input variable `project_number`, to allow assigning IAM permissions to Service Accounts in fixtures * (tests) fix not outputting the path, when object is not found in inventory * (tests) fix `create_e2e_sandbox.sh` - now it properly finds root of the repo Secret Manager * added `version_versions` output, to allow specifying versions in other modules. `versions` is sensitive and it makes it unsuitable for `for_each` values New test fixtures * `pubsub.tf` - creating one topic * `secret-credential.tf` - creating Secret Manager `credential` secret * `shared-vpc.tf` - creating two projects (host and service), and vpc in host project * `vpc-connector.tf` - creating VPC Access Connector instance Cloud Run v2 module changes * fix non-empty plan after apply when providing `volumes` with empty/null `cloud_sql_instances` * update inventory files * add additional E2E tests using fixtures
Co-authored-by: Julio Diez <[email protected]>
27b196d
to
5d0e7e4
Compare
@wiktorn can we merge this? I don't expect clarification on the last item to come anytime soon. :) |
Happy to merge it, just need a review :-) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great job :)
Global changes
project_number
forexamples
andexamples_e2e
tests to allow assigning IAM permissions to Service Accounts in fixturescreate_e2e_sandbox.sh
- now it properly finds root of the repoSecret Manager
version_versions
output, to allow specifying versions in other modules.versions
is sensitive and it makes it unsuitable forfor_each
valuesNew test fixtures
pubsub.tf
- creating one topicsecret-credential.tf
- creating Secret Managercredential
secretshared-vpc.tf
- creating two projects (host and service), and vpc in host projectvpc-connector.tf
- creating VPC Access Connector instanceCloud Run v2 module changes
region
local.trigger_sa_email
, so explicitly provided SA is passed to triggervolumes
with empty/nullcloud_sql_instances
Checklist
I applicable, I acknowledge that I have:
terraform fmt
on all modified filestools/tfdoc.py