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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(arm): add CKV_AZURE_86 to check resorce is a ContainerRegistry with tier "Standard" #6336

Open
wants to merge 16 commits into
base: main
Choose a base branch
from

Conversation

rutiNalenger
Copy link
Contributor

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Description

The function checks if a specific resource is a ContainerRegistry with tier "Standard". If so, it returns a failure result; otherwise, it returns a success result.

New/Edited policies (Delete if not relevant)

Description

Include a description of what makes it a violation and any relevant external links.

Fix

How does someone fix the issue in code and/or in runtime?

Checklist:

  • [v] My code follows the style guidelines of this project
  • [v] I have performed a self-review of my own code
  • [v] I have commented my code, particularly in hard-to-understand areas
  • [v] I have made corresponding changes to the documentation
  • [v] I have added tests that prove my feature, policy, or fix is effective and works
  • [v] New and existing tests pass locally with my changes
  • [v] Any dependent changes have been merged and published in downstream modules

Comment on lines 19 to 21
tier = properties.get("tier")

resourceType = properties.get("resourceType")
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't see tier and resourceType fields in Microsoft.ContainerRegistry/registries
Probably this is not the resource type.

@rutiNalenger
Copy link
Contributor Author

rutiNalenger commented May 21, 2024 via email

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

2 participants