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

Promote semantic to first class application #2681

Open
Ardiea opened this issue Sep 24, 2024 · 0 comments
Open

Promote semantic to first class application #2681

Ardiea opened this issue Sep 24, 2024 · 0 comments
Labels
Design DevOps Infrastructure Tasks related to infrastructure needed to power other services Tech Debt

Comments

@Ardiea
Copy link
Member

Ardiea commented Sep 24, 2024

Description/Context

The semantic stack is currently 'quick and dirty' and it has hung around far longer than it should have. Mike is tired of replacing the credentials by hand every 30 days and/or any of the other things it requires to continue running.

Plan/Design

  1. Prereq: dev needs to produce some kind of artifact or define gitrepo(s) and branch(s) to track that constituent the application.
  2. Improve the AMI bake to include code artifacts from step 0 and anything else needed, like building the .env file and probably a docker-compose file? Including consul template code to put in dynamic db creds for the .env file.
  3. Improve the pulumi code with anything it needs to support the improvements in step 1.
  4. Add nginx / traefik in front of the existing services and have it listen on 443 with a * cert from ACM or whatever. Letsencrypt is fine too. I think nginx is there already from the compose file that the app shipped with? Whatever it is, needs review and needs more TLS.
  5. Standard build+deploy pipeline.

or, depending on how long this hangs around

  1. Put this in kubernetes.
  2. More to follow?
@Ardiea Ardiea added DevOps Infrastructure Tasks related to infrastructure needed to power other services Tech Debt Design labels Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Design DevOps Infrastructure Tasks related to infrastructure needed to power other services Tech Debt
Projects
None yet
Development

No branches or pull requests

1 participant