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

Create CI/CD deployment flow for Building Blocks components #46

Open
rin-skylight opened this issue Mar 5, 2024 · 1 comment · May be fixed by CDCgov/phdi#1773
Open

Create CI/CD deployment flow for Building Blocks components #46

rin-skylight opened this issue Mar 5, 2024 · 1 comment · May be fixed by CDCgov/phdi#1773
Assignees

Comments

@rin-skylight
Copy link
Collaborator

rin-skylight commented Mar 5, 2024

Background

The home stretch! It's time to get the DIBBs components in the cloud. the VIPER set of components is half of our equation.

Action requested

Work with the VIPER team to get their components deployed in the shared CDC cluster, along with updates to the team's release workflow to automatically deploy out to us.

Acceptance Criteria

  • All VIPEr workloads exist in our cluster
  • Data processing pipeline behaves as expected

Additional context

The CI/CD integration may be achieved through GH actions OR through Octopus Deploy. If we go with the former, we may want to create another ticket for the latter to keep track of that work.

This ticket may also need to be broken apart into separate smaller resources, depending on level of complexity. @nickclyde is our best expert on that facet.

@rin-skylight rin-skylight added DevOps and removed DevOps labels Mar 5, 2024
@kplaneaux
Copy link
Collaborator

Need to decide whether we want to keep Helm integrated with terraform or decouple - design session needed!

@alismx alismx self-assigned this Apr 12, 2024
@alismx alismx linked a pull request May 21, 2024 that will close this issue
1 task
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 a pull request may close this issue.

3 participants