Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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: allow eks addons to use pod identity associations #244
base: main
Are you sure you want to change the base?
feat: allow eks addons to use pod identity associations #244
Changes from 5 commits
29af931
ee8d211
dc44e10
d510b58
2989569
f422d4d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 177 in main.tf
GitHub Actions / terraform-module / CI / Lint (.)
Check warning on line 178 in main.tf
GitHub Actions / terraform-module / CI / Lint (.)
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.
🛠️ Refactor suggestion
Refactor to address deprecated lookup usage and simplify conditions.
The implementation works but can be improved:
lookup
function with two arguments is deprecated.Apply this diff to improve the code:
The changes:
lookup
usagetry
function for safe access to potentially undefined values📝 Committable suggestion
🧰 Tools
🪛 GitHub Check: terraform-module / CI / Lint (.)
[warning] 177-177:
[tflint] reported by reviewdog 🐶
Lookup with 2 arguments is deprecated
Raw Output:
main.tf:177:29: warning: Lookup with 2 arguments is deprecated ()
[warning] 178-178:
[tflint] reported by reviewdog 🐶
Lookup with 2 arguments is deprecated
Raw Output:
main.tf:178:29: warning: Lookup with 2 arguments is deprecated ()
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.
💡 Codebase verification
Based on the results, I can now generate the final response:
Documentation needed for pod identity association feature
The implementation is functionally correct with proper AWS provider version (>= 5.75.0) support, but requires documentation updates:
🔗 Analysis chain
Implementation aligns with PR objectives.
The changes successfully add support for pod identity associations in EKS addons while maintaining backward compatibility. This provides users with an alternative to IRSA as intended.
A few points to verify:
Let me check the README content to ensure we have proper documentation for this feature.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
Length of output: 606
Script:
Length of output: 54903
🧰 Tools
🪛 GitHub Check: terraform-module / CI / Lint (.)
[warning] 177-177:
[tflint] reported by reviewdog 🐶
Lookup with 2 arguments is deprecated
Raw Output:
main.tf:177:29: warning: Lookup with 2 arguments is deprecated ()
[warning] 178-178:
[tflint] reported by reviewdog 🐶
Lookup with 2 arguments is deprecated
Raw Output:
main.tf:178:29: warning: Lookup with 2 arguments is deprecated ()
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.
🧹 Nitpick (assertive)
LGTM! Consider adding validation and improving documentation.
The implementation of
pod_identity_association
is well-structured and maintains backward compatibility. A few suggestions for enhancement:role_arn
format to ensure it's a valid IAM role ARNConsider adding these enhancements:
Update the
description
field to include: