-
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
ec2_win_password returns success when it fails to decode the password #142
Comments
Files identified in the description: If these files are inaccurate, please update the |
@fd-davidtulloh: Greetings! Thanks for taking the time to open this issue. In order for the community to handle your issue effectively, we need a bit more information. Here are the items we could not find in your description:
Please set the description of this issue with this template: |
@fd-davidtulloh I am working on this issue |
@fd-davidtulloh Could you please look into this PR ? |
Looks fantastic
…On Fri, Oct 30, 2020 at 10:23 PM nikhilpatne ***@***.***> wrote:
@fd-davidtulloh <https://github.com/fd-davidtulloh> Could you please look
into this PR ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#142 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQCIIGAYSBOHCPH4X2XG2DDSNKO4TANCNFSM4O3LHXRA>
.
|
* [BUG_FIX] ec2_win_password issue ( #142 ) * Creating a changelog fragment
* [BUG_FIX] ec2_win_password issue ( ansible-collections#142 ) * Creating a changelog fragment
* [BUG_FIX] ec2_win_password issue ( ansible-collections#142 ) * Creating a changelog fragment
* ec2_eni: Move to boto3, add support for tags and name Initial port from ansible/ansible#54950 Co-authored-by: Mike Healey <[email protected]> Co-authored-by: Tim <[email protected]> Co-authored-by: s-hertel <[email protected]> * early retry - doesn't do anything * Use random CIDR for VPC to reduce the risk of conflicts Start the ec2 instances early so we don't need to wait so long for them * Add AWSRetry to ec2_eni_info * ec2_eni_info - Add support for eni_id * Add minimal tests for ec2_eni Fix association / attachment documentation - Technically this changed with the boto2 -> boto3 migration. Since it's been this way for so long (Ansible 2.5), don't try adding backwards compatibility. * Add retries to ec2_eni * Add 'tags' as an output for ec2_eni_info for consistency * Purging IP addresses sometimes takes time. * Update version_added
SUMMARY
An unsuccessful decode call returns:
I would expect it to return a failure state
The text was updated successfully, but these errors were encountered: