Repository navigation
Deploy processor to existing ECS services and configure sales email via SSM - #1
Merged
Merged
Conversation
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.
Deploy forms-processor-v6 by registering a new task revision and updating the existing service on
topcoder-infrastructure. The release preserves service networking and task roles/resources, retains nonzero desired counts, activates an existing zero-count service, and verifies healthy tasks of the requested revision. CloudFormation is no longer part of application deployment. CircleCI gates develop/dev and master/production releases on application and deployment tests.Inject Bus API from
/config/forms-processor-v6/appvar/BUSAPI_URL, reuse Forms API database/Auth0 parameters, and use shared Kafka parameters. The sales flow reads its recipients and template only fromLETS_TALK_RECIPIENTSandLETS_TALK_SENDGRID_TEMPLATE_ID; missing values defer delivery rather than using stale database recipients. Other flows retain their database settings. Parameter changes require redeployment. The database enabled flag remains explicit.Includes the full SendGrid example in
examples/lets-talk-email.json, enablement SQL, and release/rollback guidance.payload.databecomes SendGrid dynamic template data (for example{{answers.firstname}}). Deploy the API's20261013010000_lets_talk_processor_keymigration first.Validation: lint, build, typecheck, 31 unit tests, 8 PostgreSQL integration tests, 5 deployment regression tests, and runtime Docker build passed. Workflow YAML parsed and branch/dependency mapping verified. Production deployment and live Kafka/email testing are pending reviewed merges, production credentials, and recipient/template configuration. The supplied production credentials currently resolve to the dev account. CircleCI project connection/execution remains to be confirmed.
Release dependency: topcoder-platform/forms-api-v6#6. Website cutover: https://github.com/topcoder-platform/topcoder-website/pull/56.
Dev preparation completed: created the processor BUSAPI_URL SecureString and added scoped SSM read permissions to its existing execution role. A request built from the live dev task passes AWS SDK shape validation, and IAM simulation permits all selected references. No ECS revision was registered or deployed.