Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Combine cost and tag policies comment output #2564

Merged
merged 4 commits into from
Jul 13, 2023

Conversation

tim775
Copy link
Member

@tim775 tim775 commented Jul 12, 2023

No description provided.

@tim775 tim775 requested a review from aliscott July 12, 2023 02:29
@tim775 tim775 self-assigned this Jul 12, 2023
@tim775 tim775 removed the request for review from aliscott July 12, 2023 12:21
@tim775 tim775 requested a review from aliscott July 12, 2023 20:01
Copy link
Member

@aliscott aliscott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

@@ -161,6 +161,9 @@ func ToMarkdown(out Root, opts Options, markdownOpts MarkdownOptions) ([]byte, e
"showProject": func(p Project) bool {
return showProject(p, opts, false)
},
"cloudURL": func() string {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this need to be a function?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I couldn't see another way to pass the value from the toplevel template to the sub-template.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

馃憤

@tim775 tim775 merged commit e582f63 into master Jul 13, 2023
10 checks passed
@tim775 tim775 deleted the feat/combine_cost_and_tag_policy_comment_output branch July 13, 2023 11:11
Failing Tag Policy: This should show as a failure
module.hosted_cloud_pricing_api.aws_s3_bucket.cloud_pricing_api_db_data in project(s) my-dev-project, my-other-project-with-same-violations
- should have mandatory tags: "Environment", "Team"
- should have a valid value for "Team" tag: "Ops", "Frontend team", "Backend team"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tim775 Do we want to keep this copy as is or update it to follow the same "Missing mandatory tags"/"Invalid value..." messages?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants