-
Notifications
You must be signed in to change notification settings - Fork 108
Initial set of modules #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
Initial set of modules #1
Conversation
@craigdbarber @sethvargo PTAL |
Great work! I'm adding @danawillow to this PR to solicit her feedback. She's the TLM for the gcp-terraform provider and would have a larger context to bring to bear. |
examples/gh-runner-gke-dind/main.tf
Outdated
repo_owner = var.repo_owner | ||
repo_url = var.repo_url | ||
gh_token = var.gh_token | ||
machine_type = "n1-highcpu-4" |
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.
Why hard code these VM configs? Suggest instead using variables with these as default values.
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.
This was something I was testing with, didn't intend to be part of the example. Just for some clarity- anything in examples/* is just an example of how to use the actual modules which reside in modules/*. I have used variables with sane defaults for the modules which will be what the end user directly uses.
examples/gh-runner-gke-dind/main.tf
Outdated
repo_url = var.repo_url | ||
gh_token = var.gh_token | ||
machine_type = "n1-highcpu-4" | ||
min_node_count = 3 |
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.
Variables for these please
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.
This was something I was testing with, didnt intend to be part of the example. Just for some clarity- anything in examples/* is just an example of how to use the actual modules which reside in modules/*. I have used variables with sane defaults for the modules which will be what the end user directly uses.
value = module.runner-gke.kubernetes_endpoint | ||
} | ||
|
||
output "client_token" { |
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.
Why do we need to output this?
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 use these in some of the inspec tests here.
terraform-google-github-actions-runners/test/integration/gh-runner-gke/controls/kubectl.rb
Line 19 in 53beb1d
client_token = attribute('client_token') |
d75ee86
to
598a38a
Compare
Hi All, |
…et/update-transient-deps Use GitHub sources to get master versions of dependencies
Added modules for
Added examples for