-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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: Add option allowing usage of custom policy check tools #3765
feat: Add option allowing usage of custom policy check tools #3765
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@X-Guardian I know you worked on this a bit and I was wondering if you have any input
@GenPage
| repo_locking | bool | `true` | no | Get a repository lock in this project when plan. | | ||
| repo_locking | bool | `true` | no | Get a repository lock in this project when plan. | ||
|
||
| custom_policy_check | bool | `false` | no | Enable using policy check tools other than Conftest | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could you add an example on how to use this with another tool?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jamengual Added custom-policy-checks.md
with examples for both ways to set the flag and linked to it from server-side-repo-config.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't a big fan of trying to jam custom policy check support into the existing model, however I understand the need to have support for other tooling. I'm going to leave this open for a couple weeks to gather other feedback from the community before deciding on whether to merge this as-is or not.
Updated the |
298d708
to
d29ed31
Compare
…ntis#3765) * Adding new flag everywhere relevant, implementing policy result workaround * Fixing unit test str matching, adding custom policy conditional to step_runner * Adding documentation steps for custom policy tools * Refactoring ConftestOutput attribute to PolicyOutput
…ntis#3765) * Adding new flag everywhere relevant, implementing policy result workaround * Fixing unit test str matching, adding custom policy conditional to step_runner * Adding documentation steps for custom policy tools * Refactoring ConftestOutput attribute to PolicyOutput
what
custom_policy_check
setting in repo config and atlantis.yamlcustom_policy_check
in atlantis.yamlConftestOutput
field toPolicyOutput
inPolicySetResult
struct for clarityproject_command_runner
no longer tries to parse the policy output as a JSON object directly into a struct assuming Conftest output formatwhy
approve_policies
commandtests
atlantis.yaml
override setting. Approve_policies behavior is unaffected.references