-
Notifications
You must be signed in to change notification settings - Fork 398
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
eks_nodegroup module remote_access config not working as documented #1771
Comments
This was referenced Apr 13, 2023
softwarefactory-project-zuul bot
pushed a commit
that referenced
this issue
Apr 19, 2023
…1773) eks_nodegroup - fixing remote access and added to integration tests SUMMARY Fixes #1771 Handling remote_access configuration the right way that boto understands it. Also included it to integration tests. ISSUE TYPE Bugfix Pull Request COMPONENT NAME eks_nodegroup Reviewed-by: Markus Bergholz <[email protected]> Reviewed-by: Thomas Bruckmann Reviewed-by: Mark Chappell
tremble
pushed a commit
to tremble/community.aws
that referenced
this issue
Apr 20, 2023
…nsible-collections#1773) eks_nodegroup - fixing remote access and added to integration tests SUMMARY Fixes ansible-collections#1771 Handling remote_access configuration the right way that boto understands it. Also included it to integration tests. ISSUE TYPE Bugfix Pull Request COMPONENT NAME eks_nodegroup Reviewed-by: Markus Bergholz <[email protected]> Reviewed-by: Thomas Bruckmann Reviewed-by: Mark Chappell
softwarefactory-project-zuul bot
pushed a commit
that referenced
this issue
Apr 20, 2023
…1773) (#1781) eks_nodegroup - fixing remote access and added to integration tests SUMMARY This was incorrectly merged directly into stable-5 rather than main. Fixes #1771 Handling remote_access configuration the right way that boto understands it. Also included it to integration tests. ISSUE TYPE Bugfix Pull Request COMPONENT NAME eks_nodegroup ADDITIONAL INFORMATION This is pulling #1773 from stable-5 into main Reviewed-by: Markus Bergholz Reviewed-by: Thomas Bruckmann Reviewed-by: Mark Chappell Reviewed-by: Markus Bergholz <[email protected]>
abikouo
pushed a commit
to abikouo/community.aws
that referenced
this issue
Oct 24, 2023
* Add tox labels for lint, format and unit tests * [7.0.0] Apply isort to imports * Add isort to tox * Update workflow to run isort tests * changelog
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
When I try to create a nodegroup with remote_access config as documented, I got following error:
Couldn't create Nodegroup devcluster-eu-central-1a.: Parameter validation failed: Unknown parameter in remoteAccess: "ec2_ssh_key", must be one of: ec2SshKey, sourceSecurityGroups Unknown parameter in remoteAccess: "source_sg", must be one of: ec2SshKey, sourceSecurityGroups
However when I use the suggested camelcase, I get an validation error:
msg: 'Unsupported parameters for (community.aws.eks_nodegroup) module: remote_access.ec2SshKey, remote_access.sourceSecurityGroups. Supported parameters include: ec2_ssh_key, source_sg.'
Think there needs to be a translation from unterscore ansible definition to camelcase from boto in this line, similar to "update_config":
https://github.com/ansible-collections/community.aws/blob/main/plugins/modules/eks_nodegroup.py#L518
I will try to debug further and may provide a PR if successful.
Issue Type
Bug Report
Component Name
eks_nodegroup
Ansible Version
Collection Versions
AWS SDK versions
Configuration
OS / Environment
Steps to Reproduce
Using the module quiet normal
Expected Results
No error from boto or the module itself and injected ssh key on all workers
Actual Results
Code of Conduct
The text was updated successfully, but these errors were encountered: