Skip to content

ci(deploy): take the Slack webhook as a secret so the logs mask it - #100

Open
mp-web3 wants to merge 1 commit into
mainfrom
ci-slack-webhook-secret
Open

mp-web3 wants to merge 1 commit into
mainfrom
ci-slack-webhook-secret

Conversation

@mp-web3

@mp-web3 mp-web3 commented Nov 9, 2026

Copy link
Copy Markdown

Both deploy templates (deployment-template.yaml and deploy-dev-all.yaml) take the Slack webhook as an input and put it in the job env. Every step prints that env in its log, so each deploy log shows the webhook URL. A secret passed to a reusable workflow is masked there instead.

What changes

  • New optional secret slack_webhook_url in both templates.
  • SLACK_WEBHOOK_URL in the job env reads the secret, and falls back to the slack_webhook_url input when no secret is passed.
  • The input is now optional, with an empty default, so callers that still pass it keep working. Merging this changes nothing for them.

Checked

  • actionlint is clean on both templates.
  • With the new template as a local workflow, actionlint accepts both the current callers (input) and callers that pass the secret. It reports a misspelled secret name, so the check does see the call.

Not checked: a real deploy run. The first deploy whose caller passes the secret should post the usual "deployment started" message, and its log should show SLACK_WEBHOOK_URL: ***.

🤖 Generated with Claude Code

The deploy templates put the webhook input in the job env, and every step
prints that env in its log. A secret is masked there. The input stays
optional, so callers that still pass it keep working.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.

1 participant