Skip to content
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

Don't notify willthames for AWS modules #483

Merged
merged 1 commit into from
Mar 18, 2021

Conversation

willthames
Copy link
Contributor

SUMMARY

Don't notify willthames for AWS modules

ISSUE TYPE
  • Bugfix Pull Request
COMPONENT NAME

botmeta

ADDITIONAL INFORMATION

@willthames
Copy link
Contributor Author

I'm not keeping up with Ansible for AWS so this just reflects reality

@ansibullbot ansibullbot added bug This issue/PR relates to a bug community_review needs_triage new_contributor Help guide this first time contributor small_patch Hopefully easy to review labels Mar 18, 2021
@tremble tremble merged commit cf2ff33 into ansible-collections:main Mar 18, 2021
@tremble
Copy link
Contributor

tremble commented Mar 18, 2021

Thanks for your work over the years @willthames

@willthames
Copy link
Contributor Author

thanks @tremble - very kind of you to say

@Akasurde
Copy link
Member

@willthames Thanks for working on AWS modules. I really appreciate the work you did.

@willthames
Copy link
Contributor Author

thanks @Akasurde, it was a pleasure working with you

danquixote pushed a commit to danquixote/community.aws that referenced this pull request May 16, 2021
alinabuzachis pushed a commit to alinabuzachis/community.aws that referenced this pull request Jul 19, 2021
alinabuzachis pushed a commit to alinabuzachis/community.aws that referenced this pull request Jul 19, 2021
danielcotton pushed a commit to danielcotton/community.aws that referenced this pull request Nov 23, 2021
alinabuzachis pushed a commit to alinabuzachis/community.aws that referenced this pull request May 25, 2022
…#483)

ec2_vol: Fix incorrectly returned changed result

SUMMARY
When modify_volume is used but no new disk is being attached, the module incorrectly reports that no change has occurred even when disks have been modified (iops, throughput, type, etc.). This is due to the attach function overwriting the changed variable even if no disks are attached.
Fixes ansible-collections#482
The integration test has been fixed so that when the gp3 modifications are tested, the volume is already in an attached state (previously detached) when reporting back changed. The detach tests are moved further down now, allowing this case to be properly covered by the existing assert:

  
    
      amazon.aws/tests/integration/targets/ec2_vol/tasks/tests.yml
    
    
        Lines 384 to 387
      in
      e8df917
    
    
    
    

        
          
           - name: check that volume_type has changed 
        

        
          
             assert: 
        

        
          
               that: 
        

        
          
                 - changed_gp3_volume.changed 
        
    
  


ISSUE TYPE


Bugfix Pull Request

COMPONENT NAME
ec2_vol

Reviewed-by: Alina Buzachis <None>
Reviewed-by: None <None>
Reviewed-by: Mark Chappell <None>
Reviewed-by: None <None>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue/PR relates to a bug community_review needs_triage new_contributor Help guide this first time contributor small_patch Hopefully easy to review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants