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

Allow custom resources to be used for a CiviForm deployment #7378

Closed
dkatzz opened this issue May 2, 2024 · 0 comments · Fixed by civiform/cloud-deploy-infra#327 or civiform/cloud-deploy-infra#330
Assignees
Labels
aws AWS deployment related issues ce-charlotte deploy Work for the deploy directory or to enable new deployments

Comments

@dkatzz
Copy link
Contributor

dkatzz commented May 2, 2024

Description

Currently, we create all the resources needed for CiviForm through our deployment terraform scripts. However, Charlotte has a VPC (spanning across 2 subnet groups) and load balancer they'd like traffic to hit before getting to CiviForm. We should allow our deployment to be more modular, allowing entities to set a VPC, load balancer, or other resources to use and if those are set, we'll use them, and if not we'll create them ourselves.

Notes about Charlottes environment can be found here

Describe the solution you'd like.

Allow Charlotte to use the resources they have in their environment and have those hooked into the CiviForm deployment system. More broadly, allow civic entities to enter a VPC ID and load balancer that should be used instead of the ones we normally create with the deployment.

What priority is this?

This is high priority, since it will block Charlotte's launch

Done when:

Charlotte can successfully deploy within their AWS environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment