DOE-212 Infracost integration in pipeline

[ntse]

No description provided.

[github-actions]

💰 Infracost report

Consider fixing these issues, they don't align with your company's FinOps policies & the Well-Architected Framework.

Tagging policies
🔴 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.
	resource aws_lb.this[0] provisioned by module module.alb Missing mandatory tag Environment. Must be one of Dev, Stage, Prod. Consider using default tags to avoid adding tags to individual resources. Missing mandatory tag: Service. Consider using default tags to avoid adding tags to individual resources. in project ukhsa-collaboration/devops-github-reusable-workflows/applications/hello-world-front-prd
	resource aws_ecs_service.this[0] provisioned by module module.ecs_service Missing mandatory tag Environment. Must be one of Dev, Stage, Prod. Consider using default tags to avoid adding tags to individual resources. Missing mandatory tag: Service. Consider using default tags to avoid adding tags to individual resources. Dynamically created task resources will not have tag(s) Service, Environment because tag propagation is not configured. Tag propagation should be configured by setting propagate_tags to a valid value (TASK_DEFINITION, SERVICE) in project ukhsa-collaboration/devops-github-reusable-workflows/applications/hello-world-front-prd

There are also 2 pre-existing issues in the main branch. Fix some to climb your org’s leaderboard 🥇

_{This comment will be updated when code changes.}