Repository navigation
rename enableTfOperations to preventDestructiveOperations - #525
jaylonmcshan19-x wants to merge 1 commit into
Conversation
Marin2409
left a comment
There was a problem hiding this comment.
one question just out of curiosity, is there a reason why you set preventDestructiveOperations to false in .github/workflows/helm-lint.yml and then to true in helm/terraform-mcp-server/values.yaml ?
|
@Marin2409 yeah that's intentional. values.yaml holds the real default which is true, so destructive tools are blocked unless someone opts in. the lint workflow does two template runs, one with defaults, and one with a set of overrides to hit the paths that don't render by default. setting it to false there is just proving the override works. felt worth doing on this one specifically because of the helm default filter thing, if I'd left that in then false would've come back as |
PCI review checklist
This is the chart side of the
ENABLE_TF_OPERATIONSrename for TFECO-13361. This PR swaps the env var forPREVENT_DESTRUCTIVE_OPERATIONSand the value forpreventDestructiveOperations, defaults to true so destructive tools are now blocked without any extra config.one thing I believe its worth noting, I ran into a small gotcha while doing this, the default filter treats false as empty. so if I'd
kept the
| default truepattern a user setting this to false would've gotten true back and wouldn't have known. So I dropped the filter and let thevalues.yamlsupply the default instead. I made sure to test both and true and false both render correctlyThis PR depends on TFECO-13360 landing, the env var doesn't do anything until then.
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.