terraform-google-log-export
terraform-google-log-export copied to clipboard
chore(deps): update tf modules
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| terraform-google-modules/project-factory/google (source) | module | major | ~> 10.0 -> ~> 14.0 |
| terraform-google-modules/scheduled-function/google (source) | module | major | 1.5.1 -> 2.5.0 |
Release Notes
terraform-google-modules/terraform-google-project-factory
v14.0.0
⚠ BREAKING CHANGES
- Increase to minimum TPG version 4.28 (#738)
Features
- add random_project_id_length (#735) (773ea4b)
- Add support for custom time periods in budget module (#738) (9273052)
v13.1.0
Features
- Add support to project cloud storage public access prevention (#740) (e9ba8a2)
- update test/setup to pfactory 13.0 (321bed2)
Bug Fixes
- add propagation to test/setup (#708) (321bed2)
- ensure test/setup/outputs.folder_id returns proper ID (#712) (8f72474)
v13.0.0
⚠ BREAKING CHANGES
- add upgrade guide, update provider constraints (#705)
- Add dimensions argument to consumer quota override (#683)
- replace grant_services_network_role with grant_network_role for networkUser role management (#697)
Features
- Add dimensions argument to consumer quota override (#683) (d1d7624)
- replace grant_services_network_role with grant_network_role for networkUser role management (#697) (d309270)
- setup-sa.sh use add-iam-policy-binding (#689) (616ede9)
Bug Fixes
- add upgrade guide, update provider constraints (#705) (644f596)
- update TPG version constraints to allow 4.0 and TF v0.13+ format (#700) (b66a080)
- use module release rather than repo head (#704) (522f3cc)
- VPC-SC SA destroy sequence with default SA (#691) (0e5420b)
v12.0.0
⚠ BREAKING CHANGES
- Budget module should support filtering on labels (#627)
- Minimum provider version increased to v4.5 (#627)
Features
- Add Essential Contacts support (#617) (f89e1a0)
- Budget module should support filtering on labels (#627) (44a9fec)
- expose spend_basis for budget alerts (#681) (ea3961c)
11.3.1 (2022-01-11)
Bug Fixes
- ConflictsWith in project org_id & folder_id (#676) (2e59c9a)
- grant roles/billing.viewer to the seed service account in helper. (#666) (e444e2a)
- Wrap budget_name output with length check (#673) (21871b2)
v11.3.1
v11.3.0
Features
- add network service tier setting (#640) (f5cce9e)
- update TPG version constraints to allow 4.0 (#636) (dd9beb3)
11.2.3 (2021-10-20)
Bug Fixes
11.2.2 (2021-10-13)
Bug Fixes
- Allow explicit provider configuration in module (#624) (621c527)
- billing_budget resource should use GA provider (#626) (b6d7bf1)
- Don't attempt to activate service identity for compute.googleapis.com (#628) (777092c)
11.2.1 (2021-09-23)
Bug Fixes
v11.2.3
v11.2.2
v11.2.1
v11.2.0
Features
- added the grant_services_network_role flag to control network IAM (#618) (f116dd5)
- Give VPC Access Agent Service Account for Cloud Run permissions on Shared VPC (#615) (87d2df0)
11.1.1 (2021-07-29)
Bug Fixes
v11.1.1
v11.1.0
Features
Bug Fixes
v11.0.0
⚠ BREAKING CHANGES
- Buckets now enable uniform bucket-level access by default. See the upgrade guide for details.
Features
Bug Fixes
- billing budget tests (#594) (64461a2)
- Increasing versions of null & random providers to support arm (#583) (28547ed)
- remove unused vars, add upgrade guide (#596) (e4c9b03)
10.3.2 (2021-04-05)
Bug Fixes
10.3.1 (2021-03-30)
Bug Fixes
terraform-google-modules/terraform-google-scheduled-function
v2.5.0
Features
- removal of folder should use the same time constraint used for projects (#79) (f4ab92b)
- support deletion of firewall policies attached to folders in clean up module (#76) (87037dd)
v2.4.0
Features
v2.3.0
Features
v2.2.0
Features
v2.1.0
Features
v2.0.0
⚠ BREAKING CHANGES
- add Terraform 0.13 constraint and module attribution (#50)
Features
Bug Fixes
v1.6.0
Features
Bug Fixes
1.5.1 (2020-09-02)
Bug Fixes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
- [ ] If you want to rebase/retry this PR, click this checkbox.
This PR has been generated by Mend Renovate. View repository job log here.
@renovate[bot] Thanks for the PR! 🚀 Unfortunately it looks like some of our CI checks failed. See the Contributing Guide for details.
- ⚠️check_terraform Failed Terraform check. More details below.
Running terraform fmt
Running terraform validate
terraform_validate .
Success!
The configuration is valid.
terraform_validate ./examples/bigquery/billing_account
Success!
The configuration is valid.
terraform_validate ./examples/bigquery/folder
Success!
The configuration is valid.
terraform_validate ./examples/bigquery/organization
Success!
The configuration is valid.
terraform_validate ./examples/bigquery/project
Success!
The configuration is valid.
terraform_validate ./examples/bq-log-alerting
╷
│
Warning:
Deprecated
│
│
with module.bq-log-alerting.module.bq-log-alerting.module.main.data.null_data_source.wait_for_files,
│
on .terraform/modules/bq-log-alerting.bq-log-alerting.main/main.tf line 32, in data "null_data_source" "wait_for_files":
│
32: data "null_data_source" "wait_for_files"
{
│
│
The null_data_source was historically used to construct intermediate values
│
to re-use elsewhere in configuration, the same can now be achieved using
│
locals
╵
╷
│
Warning:
Attribute Deprecated
│
│
with module.bq-log-alerting.random_string.service_account,
│
on ../../modules/bq-log-alerting/main.tf line 30, in resource "random_string" "service_account":
│
30: number =
"false"
│
│
**NOTE**: This is deprecated, use `numeric` instead.
╵
Success!
The configuration is valid, but there were some
validation warnings as shown above.
terraform_validate ./examples/datadog-sink
Success!
The configuration is valid.
terraform_validate ./examples/logbucket/folder
Success!
The configuration is valid.
terraform_validate ./examples/logbucket/organization
Success!
The configuration is valid.
terraform_validate ./examples/logbucket/project
Success!
The configuration is valid.
terraform_validate ./examples/pubsub/billing_account
Success!
The configuration is valid.
terraform_validate ./examples/pubsub/folder
Success!
The configuration is valid.
terraform_validate ./examples/pubsub/organization
Success!
The configuration is valid.
terraform_validate ./examples/pubsub/project
Success!
The configuration is valid.
terraform_validate ./examples/splunk-sink
Success!
The configuration is valid.
terraform_validate ./examples/storage/billing_account
Success!
The configuration is valid.
terraform_validate ./examples/storage/folder
Success!
The configuration is valid.
terraform_validate ./examples/storage/organization
Success!
The configuration is valid.
terraform_validate ./examples/storage/project
Success!
The configuration is valid.
terraform_validate ./modules/bigquery
Success!
The configuration is valid.
terraform_validate ./modules/bq-log-alerting
╷
│
Warning:
Attribute Deprecated
│
│
with random_string.service_account,
│
on main.tf line 30, in resource "random_string" "service_account":
│
30: number =
"false"
│
│
**NOTE**: This is deprecated, use `numeric` instead.
╵
╷
│
Warning:
Deprecated
│
│
with module.bq-log-alerting.module.main.data.null_data_source.wait_for_files,
│
on .terraform/modules/bq-log-alerting.main/main.tf line 32, in data "null_data_source" "wait_for_files":
│
32: data "null_data_source" "wait_for_files"
{
│
│
The null_data_source was historically used to construct intermediate values
│
to re-use elsewhere in configuration, the same can now be achieved using
│
locals
╵
Success!
The configuration is valid, but there were some
validation warnings as shown above.
terraform_validate ./modules/logbucket
Success!
The configuration is valid.
terraform_validate ./modules/pubsub
Success!
The configuration is valid.
terraform_validate ./modules/storage
Success!
The configuration is valid.
terraform_validate ./test/fixtures/bigquery/folder
Success!
The configuration is valid.
terraform_validate ./test/fixtures/bigquery/organization
Success!
The configuration is valid.
terraform_validate ./test/fixtures/bigquery/project
Success!
The configuration is valid.
terraform_validate ./test/fixtures/bq-log-alerting
╷
│
Warning:
Deprecated
│
│
with module.bq-log-alerting.module.bq-log-alerting.module.main.data.null_data_source.wait_for_files,
│
on .terraform/modules/bq-log-alerting.bq-log-alerting.main/main.tf line 32, in data "null_data_source" "wait_for_files":
│
32: data "null_data_source" "wait_for_files"
{
│
│
The null_data_source was historically used to construct intermediate values
│
to re-use elsewhere in configuration, the same can now be achieved using
│
locals
╵
╷
│
Warning:
Attribute Deprecated
│
│
with module.bq-log-alerting.random_string.service_account,
│
on ../../../modules/bq-log-alerting/main.tf line 30, in resource "random_string" "service_account":
│
30: number =
"false"
│
│
**NOTE**: This is deprecated, use `numeric` instead.
╵
Success!
The configuration is valid, but there were some
validation warnings as shown above.
terraform_validate ./test/fixtures/computed_values
Success!
The configuration is valid.
terraform_validate ./test/fixtures/pubsub/folder
Success!
The configuration is valid.
terraform_validate ./test/fixtures/pubsub/organization
Success!
The configuration is valid.
terraform_validate ./test/fixtures/pubsub/project
Success!
The configuration is valid.
terraform_validate ./test/fixtures/storage/folder
Success!
The configuration is valid.
terraform_validate ./test/fixtures/storage/organization
Success!
The configuration is valid.
terraform_validate ./test/fixtures/storage/project
Success!
The configuration is valid.
terraform_validate ./test/setup
╷
│
Error:
Failed to query available provider packages
│
│
Could not retrieve the list of available versions for provider
│
hashicorp/google: no available releases match the given constraints >=
│
3.43.0, >= 3.50.0, ~> 3.53.0, ~> 4.28, < 5.0.0
╵
╷
│
Error:
Failed to query available provider packages
│
│
Could not retrieve the list of available versions for provider
│
hashicorp/google-beta: no available releases match the given constraints >=
│
3.43.0, >= 3.50.0, ~> 3.53.0, ~> 4.11, ~> 4.28, < 5.0.0
╵
Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.
@renovate[bot]
Thanks for the PR! 🚀
✅ Lint checks have passed.