Configure Renovate

[renovate]

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

---

Detected Package Files

• versions.tf (terraform)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding PR is merged
• Show all Merge Confidence badges for pull requests.
• Enable Renovate Dependency Dashboard creation.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Ignore node_modules, bower_components, vendor and various test/tests directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

---

What to Expect

It looks like your repository dependencies are already up-to-date and no Pull Requests will be necessary right away.

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

---

This PR has been generated by Mend Renovate. View repository job log here.

[tamr-teamcity]

This PR doesn't appear to be linked to a DevOps/SRE jira ticket

[tamr-teamcity]

This PR doesn't appear to be linked to a DevOps/SRE jira ticket

[tamr-teamcity]

This PR doesn't appear to be linked to a DevOps/SRE jira ticket

[tamr-teamcity]

This PR doesn't appear to be linked to a DevOps/SRE jira ticket

[tamr-teamcity]

This PR doesn't appear to be linked to a DevOps/SRE jira ticket

[tamr-teamcity]

This PR doesn't appear to be linked to a DevOps/SRE jira ticket

[tamr-github-integrator]

[tfsec] Results

Failed: 9 issue(s)

#	ID	Severity	Title	Location	Description
1	google-compute-enable-shielded-vm-im	MEDIUM	Instances should have Shielded VM integrity monitoring enabled	main.tf:43-98	Instance does not have shielded VM integrity monitoring enabled.
2	google-compute-enable-shielded-vm-vtpm	MEDIUM	Instances should have Shielded VM VTPM enabled	main.tf:43-98	Instance does not have VTPM for shielded VMs enabled.
3	google-compute-no-project-wide-ssh-keys	MEDIUM	Disable project-wide SSH keys for all instances	main.tf:43-98	Instance allows use of project-level SSH keys.
4	google-compute-vm-disk-encryption-customer-key	LOW	VM disks should be encrypted with Customer Supplied Encryption Keys	main.tf:50-56	Instance disk encryption does not use a customer managed key.
5	google-compute-enable-shielded-vm-im	MEDIUM	Instances should have Shielded VM integrity monitoring enabled	main.tf:43-98	Instance does not have shielded VM integrity monitoring enabled.
6	google-compute-enable-shielded-vm-vtpm	MEDIUM	Instances should have Shielded VM VTPM enabled	main.tf:43-98	Instance does not have VTPM for shielded VMs enabled.
7	google-compute-no-default-service-account	CRITICAL	Instances should not use the default service account	main.tf:79	Instance uses the default service account.
8	google-compute-no-project-wide-ssh-keys	MEDIUM	Disable project-wide SSH keys for all instances	main.tf:43-98	Instance allows use of project-level SSH keys.
9	google-compute-vm-disk-encryption-customer-key	LOW	VM disks should be encrypted with Customer Supplied Encryption Keys	main.tf:50-56	Instance disk encryption does not use a customer managed key.

[tamr-github-integrator]

No problems detected!

[tamr-github-integrator]

No problems detected!

[tamr-github-integrator]

No problems detected!

[tamr-github-integrator]

No problems detected!