OC-923: Integrate PoC ECS infrastructure with octopus #729
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
karmseveeratjisc
requested changes
Dec 6, 2024
karmseveeratjisc
approved these changes
Dec 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The purpose of this PR was to work a proof of concept ECS setup I made separately into octopus's codebase. The terraform code creates:
The proof of concept just logs a simple message.
There is one per environment because the idea is that this infrastructure will be used to run scripts against each environment like the ARI import script.
Acceptance Criteria:
The proof of concept ECS setup can be deployed and run within octopus's environment.
Checklist:
Screenshots:
Service running on int
Service running on prod
