fix: forward Telegram access code to production - #171
Merged
Conversation
- Forward TELEGRAM_ACCESS_CODE to the production deployment - Serialize the access code in the remote Compose environment - Add a contract test for workflow secret propagation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Forward the configured Telegram access code through the production deployment.
Why
The secret exists in GitHub Actions production configuration, but the deployment did not pass it to the container, so access gating and identity capture stayed disabled.
How
TELEGRAM_ACCESS_CODEfrom production secrets in the deploy step.write_compose_env.pyserialization arguments.Tests
uv run pytest tests/test_deployment_contract.py -quv run ruff formatuv run ruff checkuv run mypy .uv run pytest --cov=src(1607 passed, 1 skipped, 100% coverage)Related Issues