-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
support EKS logs #337
Comments
it has been released as provider v2.6.0 :) |
And merged. Please test and I'll make a release soon. |
Sure, I will do a quick check on this today. |
BTW, if we want to release, we need to update the provider version in here too: |
I'm closing this issue |
I forgot to update here, I have run with aws provider 2.6.0 for last weekend without any issue. |
@max-rocket-internet I think we do need to enforce the provider version with the new feature of eks logs. |
@chenrui333 the question is how? according to the https://github.com/terraform-aws-modules/terraform-aws-eks/pull/347/files , we only update example how to use the module |
yeah, indeed, I was think of enforcing the module version in the module level. You might be interested with this issue I submitted, hashicorp/terraform#20996 |
Indeed. I'm not sure how though. I think in the past we had providers defined inside the module itself but then TF community moved away from this I think? |
Already had a issue for this: #348 |
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'm submitting a...
What is the current behavior?
We depend on the issue 8204, but when that is implemented, we can configure logs for EKS.
What's the expected behavior?
Are you able to fix this problem and submit a PR? Link here if you have already.
Not yet
Environment details
Terraform v0.11.13
Any other relevant info
At the moment, we don't have requirements for AWS provider (correct me if I'm mistaken) but right now this module can't work with >v2.2 anyway (cluster_endpoints).
EDIT: Any suggestions on how to make provider aws version as a requirement?
The text was updated successfully, but these errors were encountered: