Summary
The Synvya Keycast deployment helpers still load the service token from the old AWS Secrets Manager path:
synvya//event-processor/service-token
The service has been renamed to server, and the target secret path should become:
synvya//server/service-token
Current references
- scripts/load-secrets.sh
- docker-compose.synvya.yml (variable naming still reflects EP_SERVICE_TOKEN)
Requested change
- Update the Keycast Synvya deployment helpers to read the new server/service-token secret path
- Rename related env var naming where appropriate for clarity
- Keep backward compatibility in rollout if needed, but make server/service-token the canonical path
Context
The old secret will be duplicated temporarily to avoid breaking existing deployment flows, but the repository should be updated so future deploys do not depend on the legacy event-processor naming.
Summary
The Synvya Keycast deployment helpers still load the service token from the old AWS Secrets Manager path:
synvya//event-processor/service-token
The service has been renamed to server, and the target secret path should become:
synvya//server/service-token
Current references
Requested change
Context
The old secret will be duplicated temporarily to avoid breaking existing deployment flows, but the repository should be updated so future deploys do not depend on the legacy event-processor naming.