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

Refactor hard-coded FQDN's in CloudFormation templates #240

Open
3 tasks
MikeTheCanuck opened this issue Jun 8, 2019 · 1 comment
Open
3 tasks

Refactor hard-coded FQDN's in CloudFormation templates #240

MikeTheCanuck opened this issue Jun 8, 2019 · 1 comment

Comments

@MikeTheCanuck
Copy link
Contributor

Summary

With #239, we'll need the ability to substitute a different Host value in one place in the master template for each of staging and production (and any test environments we create). Until then, I'll be chasing down all the various instances of the predictable strings in hard-to-reach places.

Impact

Impacts S5.

Tasks

  • Decide on naming convention for staging URLs
  • Instantiate DNS records for staging domains
  • Create the variable, declare their values, substitute for the various Host values scattered throughout

Definition of Done

Test environments can be deployed with the new parameterized Host values.

@MikeTheCanuck
Copy link
Contributor Author

The Host values to be managed:

  • service.civicpdx.org - domain for all API containers
  • 2017.civicpdx.org/ civicpdx.org - domains for the container hosting the React applications from the 2017 project season
  • civicplatform.org - domain for the container hosting the React applications from the 2018 project season

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

No branches or pull requests

1 participant