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

Convert to Actions #289

Merged
merged 5 commits into from
Mar 18, 2024
Merged

Convert to Actions #289

merged 5 commits into from
Mar 18, 2024

Conversation

jason-jackson
Copy link
Contributor

Changed (non-breaking)

  • Convert to Github actions

Feature PR Checklist

  • Documentation (README, local.env.dist, etc.)
  • Unit tests created or updated (see test.bats file)

Release PR Checklist

  • Update version number in ecs-deploy script
  • Give the PR a title of Release _._._ - Summary of change (using whatever
    the new version number is, plus a succinct summary of what changed)

@jason-jackson jason-jackson requested a review from a team March 18, 2024 15:04
Copy link
Contributor

@briskt briskt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

needs one tweak to the README

README.md Outdated

ecs-deploy -c production1 -n doorman-api -i my.private.repo/doorman-api -e CI_TIMESTAMP
ecs-deploy -c CLUSTERNAME -n SERVICENAME -i my.private.repo.com/frontend_container:latest -e CI_TIMESTAMP
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you're using the -e option, you probably shouldn't supply a tag (e.g. latest).

so that each task definition refers to a unique docker image/tag. This gives us the
ability to revert/rollback changes by just selecting a previous task definition and
updating the service. We plan to add a revert command/option to ecs-deploy to simplify this further.
For example, we want to use a unique docker image/tag for each task definition. This
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good

@jason-jackson jason-jackson requested review from briskt and a team March 18, 2024 15:34
README.md Show resolved Hide resolved
@jason-jackson jason-jackson merged commit 83ee092 into develop Mar 18, 2024
2 checks passed
@jason-jackson jason-jackson deleted the feature/actions branch March 18, 2024 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants