-
Notifications
You must be signed in to change notification settings - Fork 5
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
restructure TF-managed services #354
Conversation
for more information, see https://pre-commit.ci
b280290
to
b08eefb
Compare
for more information, see https://pre-commit.ci
tf-managed/README.md
Outdated
# Structure | ||
|
||
``` | ||
├── common <- common code, shared between all modules (TODO maybe move it to modules?) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this folder structure. The only change I would make is to rename common
to something like scripts
, to show more intention on the folder itself. Since the root directory is tf-managed
, we can assume that modules refer to terraform modules and either grow the scripts folder, which is then split by script language (i.e. ruby). Just a thought!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@joshdougall Will do, thanks for the review. The end goal is to get rid of this directory altogether and hide all those scripts behind a docker (and/or packer!) images.
for more information, see https://pre-commit.ci
4988256
to
b389d93
Compare
b389d93
to
4c78c91
Compare
Forest: Snapshot Service Infrastructure Plan: successShow Plan
|
Forest: Sync Check Service Infrastructure Plan: successShow Plan
|
70c3bbe
to
ef63832
Compare
e31f8ed
to
793b611
Compare
793b611
to
f93ef18
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
The structure seems nice and straightforward.
nit: I'm not convinced on live
directory naming though, if those are terragrunt configs - just name it terragrunt
instead?
GH if
conditions are surely a pain to test, but I can see no way around it, as long as those have been tested.
Same goes for wget
of deps, not a problem to re-run the job if it ever fails.
This follows the structure outlined in Terraform Up and Running and the Terragrunt guide ![]() |
Let's keep it as is then. Still not a fan of the naming though :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Summary of changes
Changes introduced in this pull request:
Migrated services:
Follow-ups:
snapshot service
) with a singlecount = N
. Allow multiple instances of a single module #372(and some more that are not linked)
Reference issue to close (if applicable)
Closes #363
Closes #318
Other information and links