-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
feat: Replace the local-exec script with a http datasource for waiting cluster #1339
feat: Replace the local-exec script with a http datasource for waiting cluster #1339
Conversation
57e5cbd
to
ddb43fa
Compare
@shoekstra @daroga0002 @jlpettersson can you please help me to test this ? |
Maybe @xavfernandez could help to review and test this ? |
README.md
Outdated
@@ -221,6 +219,7 @@ MIT Licensed. See [LICENSE](https://github.com/terraform-aws-modules/terraform-a | |||
| [aws_iam_policy_document.workers_assume_role_policy](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/iam_policy_document) | data source | | |||
| [aws_iam_role.custom_cluster_iam_role](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/iam_role) | data source | | |||
| [aws_partition.current](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/partition) | data source | | |||
| [http_http.wait_for_cluster](https://registry.terraform.io/providers/hashicorp/http/latest/docs/data-sources/http) | data source | |
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.
How to change this url ?
Tested IRSA example with adding some explicit kubernetes resource creation:
I spin cluster few times and each time created with success. |
@barryib would it be possible to expose the new |
@stevehipwell What do you mean by that ? Do you want me to add a new output for data.wait_for_cluster ? |
@barryib yes that's what I mean. Although in the context of the module it's the control plane not the cluster that's ready which is why I suggested the output name be changed. |
Normally when you use cluster_id or kubeconfig outputs, you don't need bother yourself with another |
@barryib we don't use the kubeconfig output and prefer to use |
I guess we could use |
This now shipped in v16.0.0 |
@barryib the Forked http module does not have a darwin_arm64 release, I can't use this module on my M1 MacBook, I've created a PR to build releases with Go 1.16. Please take a look terraform-aws-modules/terraform-provider-http#5 |
…g cluster (terraform-aws-modules#1339) NOTES: Using the [terraform-aws-modules/http](https://registry.terraform.io/providers/terraform-aws-modules/http/latest) provider is a more platform agnostic way to wait for the cluster availability than using a local-exec. With this change we're able to provision EKS clusters and manage the `aws_auth` configmap while still using the `hashicorp/tfc-agent` docker image.
…g cluster (terraform-aws-modules#1339) NOTES: Using the [terraform-aws-modules/http](https://registry.terraform.io/providers/terraform-aws-modules/http/latest) provider is a more platform agnostic way to wait for the cluster availability than using a local-exec. With this change we're able to provision EKS clusters and manage the `aws_auth` configmap while still using the `hashicorp/tfc-agent` docker image.
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
PR o'clock
Description
In this PR we drop the usage of local-exec. But we need hashicorp/terraform-provider-http#29.
We decided to fork the terraform-provider-http provider (the PR is almost a year) into the terraform-aws-modules organization for internal usage only. The provider is published at https://registry.terraform.io/providers/terraform-aws-modules/http/latest
Related also to #1253
Test
This is still a proof of concept. I tested it locally and so far so good. I've got this kind of output during my tests.
It took 2m32s for
module.eks.data.http.wait_for_cluster[0]
to clomplete.Todo