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.

Sign up for GitHub

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

Jump to bottom

Separate Bedrock deployment configuration into it's own repository #64

Open
kylehuntsman opened this issue May 18, 2022 · 0 comments
Open

Separate Bedrock deployment configuration into it's own repository #64

kylehuntsman opened this issue May 18, 2022 · 0 comments
Assignees
@hannahhoward

Comments

@kylehuntsman
Copy link
Collaborator

kylehuntsman commented May 18, 2022 •
edited
Loading

The Bedrock deployment configuration doesn't make sense for cross-team use cases, and should therefore be pulled out into a Bedrock specific repository for managing the Bedrock development instance.

  • Autoretrieve container building to ECR on push to master will stay in the autoretrieve repository. For now we'll leave the ECR in the STI account. We might want to move this later to something ARG owns?
  • Kubernetes deployment manifests and CD will be moved to a new Bedrock specific repository. It will then just make PRs to that repo's cd/dev branch and deploy to the same sti-dev cluster it's being deployed to now.
@hannahhoward hannahhoward self-assigned this Jun 24, 2022
@hannahhoward hannahhoward moved this from Backlog to Code Complete in Autoretrieve Task Board Jul 1, 2022
@hannahhoward hannahhoward moved this from Code Complete to Done in Autoretrieve Task Board Jul 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hannahhoward hannahhoward

Labels
None yet
Projects
Autoretrieve Task Board
Status: Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hannahhoward @kylehuntsman