Skip to content

Set AMI to debian for staging and prod deployment#6583

Merged
dakotabenjamin merged 1 commit into
developfrom
fix/circleci-ami-default
Oct 21, 2024
Merged

Set AMI to debian for staging and prod deployment#6583
dakotabenjamin merged 1 commit into
developfrom
fix/circleci-ami-default

Conversation

@dakotabenjamin

Copy link
Copy Markdown
Member

What type of PR is this? (check all applicable)

  • 🍕 Feature
  • 🐛 Bug Fix
  • 📝 Documentation
  • 🧑‍💻 Refactor
  • ✅ Test
  • 🤖 Build or CI
  • ❓ Other (please specify)

Describe this PR

This change sets the deployment backend server environment to use debian AMI

@sonarqubecloud

sonarqubecloud Bot commented Oct 1, 2024

Copy link
Copy Markdown

@ramyaragupathy ramyaragupathy added this to the v4.8.2 milestone Oct 8, 2024
@dakotabenjamin dakotabenjamin merged commit 954f341 into develop Oct 21, 2024
Comment thread .circleci/config.yml
gitsha: $CIRCLE_SHA1
stack_name: "tm4-production"
host_ami: "/aws/service/canonical/ubuntu/server/20.04/stable/current/amd64/hvm/ebs-gp2/ami-id"
host_ami: "/aws/service/debian/release/11/20240813-1838/amd64"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Why not /aws/service/debian/release/11/latest/amd64 (currently set to the 2024-10-07 Debian image)?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

My logic is that using latest could introduce a breaking or unintended change. Even at a low chance I would rather avoid it, and this code is going to be depreciated soon anyways so no long-term planning needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants