Skip to content

rename enableTfOperations to preventDestructiveOperations - #525

Open
jaylonmcshan19-x wants to merge 1 commit into
mainfrom
rename-tf-operations-chart-value
Open

jaylonmcshan19-x wants to merge 1 commit into
mainfrom
rename-tf-operations-chart-value

Conversation

@jaylonmcshan19-x

@jaylonmcshan19-x jaylonmcshan19-x commented Sep 14, 2026 •

Copy link
Copy Markdown
Contributor

PCI review checklist

This is the chart side of the ENABLE_TF_OPERATIONS rename for TFECO-13361. This PR swaps the env var for PREVENT_DESTRUCTIVE_OPERATIONS and the value for preventDestructiveOperations, 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 true pattern a user setting this to false would've gotten true back and wouldn't have known. So I dropped the filter and let the values.yaml supply the default instead. I made sure to test both and true and false both render correctly

This 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.

@Marin2409 Marin2409 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

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 ?

@jaylonmcshan19-x

Copy link
Copy Markdown
Contributor Author

@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
true and the override run really wouldn't have caught it.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants