You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
Describe the bug
When running aws-cli with the ruamel-yaml lib (0.17.29+), it fails to parse the kubeconfig file when executing
eks update-kubeconfig
more than once.Expected Behavior
Expected to update the kubeconfig with the new cluster configuration.
Current Behavior
Reproduction Steps
Possible Solution
The
ruamel.yaml.resolver.BaseResolver.DEFAULT_MAPPING_TAG
value used to be a string, but it was changed to a Tag struct: https://sourceforge.net/p/ruamel-yaml/tickets/467/This broke the YAML parser the aws-cli uses to read the kubeconfig file:
aws-cli/awscli/customizations/eks/ordered_yaml.py
Lines 22 to 34 in b9eda72
This problem can be solved by casting the
DEFAULT_MAPPING_TAG
to a string, as suggested by this ticket:Additional Information/Context
No response
CLI version used
aws-cli/2.11.25 Python/3.11.4 Linux/5.4.231-137.341.amzn2.x86_64 source/x86_64.alpine.3 prompt/off
Environment details (OS name and version, etc.)
alpine:3.18
The text was updated successfully, but these errors were encountered: