Skip to content
This repository has been archived by the owner on Jan 5, 2022. It is now read-only.

Decide AWS Stage, Prod Environments Deployment Mechanism via Terraform #120

Closed
cmharlow opened this issue Jun 25, 2018 · 2 comments
Closed

Decide AWS Stage, Prod Environments Deployment Mechanism via Terraform #120

cmharlow opened this issue Jun 25, 2018 · 2 comments
Labels
(dev)ops
Milestone
RIALTO Core in St...

Comments

@cmharlow
Copy link
Contributor

How does code trigger changes to terraform to appropriate AWS environment?

Blocked by #87 Blocked by #119
@cmharlow cmharlow added this to the RIALTO Core in Stage, Prod milestone Jun 25, 2018
@cmharlow cmharlow mentioned this issue Jun 25, 2018
Closed
@cmharlow cmharlow mentioned this issue Jul 10, 2018
Closed
@aaron-collier
Copy link
Contributor

aaron-collier commented Jul 12, 2018 •
edited
Loading

Capturing this here, but will also review wiki locations: As of 7/12/18 - Neptune is not fully supported by Terraform. It is in progress but still an open ticket.

@peetucket peetucket mentioned this issue Jul 24, 2018
Open
@mjgiarlo mjgiarlo added ready and removed blocked labels Aug 2, 2018
@mjgiarlo
Copy link
Member

mjgiarlo commented Aug 2, 2018

This is decided for all TF envs (Dev, Stage, and Prod): ops will apply TF updates after they merge PRs. Is/will be documented here: https://consul.stanford.edu/display/dlssdevops/Terraform+and+AWS

Closing.

@mjgiarlo mjgiarlo closed this as completed Aug 2, 2018
@mjgiarlo mjgiarlo removed the ready label Aug 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
(dev)ops
Projects
None yet
Milestone
RIALTO Core in Stage, Prod
Development

No branches or pull requests
3 participants
@mjgiarlo @aaron-collier @cmharlow