Skip to content

Omit sensitive_vars values from TF_LOG=debug output - #451

Merged
heroku-johnny merged 1 commit into
masterfrom
fix-sensitive-variables
Sep 11, 2026
Merged

heroku-johnny merged 1 commit into
masterfrom
fix-sensitive-variables

Conversation

@heroku-johnny

Copy link
Copy Markdown
Contributor

Extends the fix from #362 to the three resources it did not cover.

heroku_config, heroku_app_config_association, and heroku_pipeline_config_var were logging the full contents of sensitive_vars maps when running with TF_LOG=debug, disclosing variable values in plaintext. This changes those log statements to output only the variable names, consistent with the behavior introduced in #362 for heroku_app.

Changes

  • heroku_config — resourceHerokuConfigCreate and resourceHerokuConfigUpdate no longer log sensitive var values
  • heroku_app_config_association — getSensitiveVars and updateVars no longer log sensitive var values
  • heroku_pipeline_config_var — resourceHerokuPipelineConfigVarRead and updatePipelineConfigVars no longer log sensitive var values

heroku_config, heroku_app_config_association, and heroku_pipeline_config_var
were logging the full contents of sensitive_vars maps. Log only the variable
names so values are never written to debug output.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
@heroku-johnny
heroku-johnny requested a review from a team as a code owner September 11, 2026 17:30
@heroku-johnny
heroku-johnny requested a review from mars September 11, 2026 17:31
@heroku-johnny
heroku-johnny merged commit 285369e into master Sep 11, 2026
8 checks passed
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.

2 participants