Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: add Aselo->Beacon integration stub Lambda code [CHI-3225] #830

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

GPaoloni
Copy link
Collaborator

@GPaoloni GPaoloni commented Feb 20, 2025

This PR is related to https://github.com/techmatters/infrastructure-config/pull/417.

Description

This PR:

  • Adds stub Lambda code for Aselo->Beacon integration under lambdas/custom-integrations/uscr-dispatcher.
  • Tweeks deploy Lambda action:
    • If a Lambda has a corresponding entry in .github/workflows/config/lambda-specific-region-map.json specifying which regions should it be deployed to, that's used.
    • Uses the default regions specified in .github/workflows/config/environment-region-map.json otherwise.

Checklist

Verification steps

AFTER YOU MERGE

  1. Cut a release tag using the GitHub workflow. Wait for it to complete and notify in the #aselo-deploys Slack channel.
  2. Comment on the ticket with the release tag version AND any additional instructions required to configure an environment to test the changes.
  3. Only then move the ticket into the QA column in JIRA

You are responsible for ensuring the above steps are completed. If you move a ticket into QA without advising what version to test, the QA team will assume the latest tag has the changes. If it does not, the following confusion is on you! :-P

@GPaoloni GPaoloni requested a review from stephenhand February 21, 2025 20:00
@GPaoloni GPaoloni marked this pull request as ready for review February 21, 2025 20:00
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