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

Add orchestration resources to Terraform #30

Merged
merged 32 commits into from
Nov 13, 2023
Merged

Conversation

emmastephenson
Copy link
Collaborator

@emmastephenson emmastephenson commented Nov 9, 2023

PULL REQUEST

Summary

Adds the orchestration service to our TF-managed Helm deployments. This means the orchestration service is now up and running live! You can see it on dev.

Related Issue

Fixes #821

Additional Information

There are a number of related changes in phdi-charts, but those have all been merged.

Some followup actions - the newly named orchestration Service resource didn't redeploy when I pushed the new chart version, I had to destroy/recreate manually. Could be another argument for something like ArgoCD.

ingestion = "ingestion-chart",
ingress = "ingress-chart",
message-parser = "message-parser-chart",
orchestration = "orchestration",
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

note: orchestration-chart didn't work because the name kept cutting off right at orchestration- and TF would complain that it was an invalid name. The solution here was to rename the chart at the Helm level, and create this mapping to track microservice name <=> chart name.


set {
name = "image.tag"
value = "latest"
value = "v1.1.1"
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

The latest version of each Docker image wasn't being picked up by Terraform, so each deployment was at a wildly different image version (whatever had been latest when the service was first deployed). The workflow to make changes is therefore:

  • Make your changes to the Docker container
  • Publish changes as new release version
  • Update this image tag
  • Push these changes and re-deploy to desired env

@emmastephenson emmastephenson merged commit 5fff7de into main Nov 13, 2023
5 checks passed
@emmastephenson emmastephenson deleted the 821/add-orchestration branch November 13, 2023 20:02
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.

2 participants