Test mig infra change

[yhna940]

No description provided.

[github-actions]

Infracost report

💰 Monthly cost will not change

Project	Cost change	New monthly cost
yhna940/gcp-mig-github-action-runner	$0	$0.06

Cost details

──────────────────────────────────
Project: yhna940/gcp-mig-github-action-runner

~ module.runner-mig.module.mig.google_compute_region_instance_group_manager.mig
  $0.00 ($0.00 → $0.00)

    ~ Instance usage (Linux/UNIX, on-demand, n1-standard-1 → c3-highcpu-176)
      $0.00 ($0.00 → $0.00)

Monthly cost change for yhna940/gcp-mig-github-action-runner
Amount:  $0.00 ($0.06 → $0.06)
Percent: 0%

──────────────────────────────────
Key: ~ changed, + added, - removed

11 cloud resources were detected:
∙ 4 were estimated, 3 of which include usage-based costs, see https://infracost.io/usage-file
∙ 6 were free, rerun with --show-skipped to see details
∙ 1 is not supported yet, rerun with --show-skipped to see details

Governance checks

🔴 1 failure

FinOps tags: This example Tagging policy shows how you can enforce required FinOps tag keys/values in pull requests. This example checks for the tags 'Service' (can have any value) and 'Environment' (must be Dev/Stage/Prod) on all taggable resources being changed in the pull request. You can adjust it from https://dashboard.infracost.io > Governance > Tagging policies. You have a 14 day trial of this feature as it's part of Infracost Cloud.

module.runner-mig.module.mig_template.google_compute_instance_template.tpl at main.tf:1 Missing mandatory tags: Service, Environment in project yhna940/gcp-mig-github-action-runner

🟢 49 passed

48 FinOps policies, 0 Tagging policies, and 1 Guardrail passed.

_{View in Infracost Cloud. This comment will be updated when code changes.}