-
-
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
how to disable windows support #582
Comments
I'm getting the same error. This causes any plan action to fail... |
@liwei0802 You can just tie your module to the previous version and it should work. |
Maybe @hodduc can take a look since they made the windows PR 🙂 |
🤔.. If you are using cluster_version <= 1.13, there is no AMI for that cluster version, but terraform will try to find it and fail. ( hashicorp/terraform#16380 ). I missed that case. A possible workaround: Set |
I think there can be two fix:
@max-rocket-internet Does this looks fine? |
That doesn't sound super elegant. Can you add some conditions into Maybe something like this?
|
Can this be re-opened? This still happens with the basic example with these versions
event with
I used |
This happened to me today on cluster_version of 1.20 |
I just opened #1371 to address this. Will you please review it and test it ? |
I'm going to lock this issue 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 similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
I have issues
when i run 'terraform plan' its poping up error message below. I am just thinking how can we simple disable windows support?
Error: Your query returned no results. Please change your search criteria and try again.
on .terraform/modules/my-cluster/terraform-aws-modules-terraform-aws-eks-55ff38c/data.tf line 32, in data "aws_ami" "eks_worker_windows":
32: data "aws_ami" "eks_worker_windows" {
I'm submitting a...
What is the current behavior?
If this is a bug, how to reproduce? Please include a code sample if relevant.
What's the expected behavior?
Are you able to fix this problem and submit a PR? Link here if you have already.
Environment details
Any other relevant info
The text was updated successfully, but these errors were encountered: