-
Notifications
You must be signed in to change notification settings - Fork 1
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
DRAFT: Split eks creation to own module #9
Conversation
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! What I'm missing here is how these modules are called from the "home directory"
I assume there's a main.tf
outside of the modules page? Or does TF just auto call these modules?
filter { | ||
name = "vpc-id" | ||
values = ["vpc-0f30cfca319ebc521"] | ||
name = "tag:Name" |
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.
Thats cool, i didn't realize you could access the tag here
@thomasyu888 For testing I manually created 2 new stacks in Spacelift to deploy this out: The difference between the 2 stacks is that they're pointing to this feature branch and specific project root: In a later PR I will plan to replace our current airflow deployment method with these 2 modules. I'll also want to make an airflow module we can attach to the stacks as well. In addition I'd like to make sure spacelift resources configured by terraform scripts. |
No description provided.