-
Notifications
You must be signed in to change notification settings - Fork 342
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
Prep 3.2.0 release #759
Prep 3.2.0 release #759
Conversation
Build succeeded.
|
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.
A little concerned that we backported a breaking change, but otherwise LGTM
changelogs/changelog.yaml
Outdated
breaking_changes: | ||
- aws_ssm - on_denied and on_missing now both default to error, for consistency | ||
with both aws_secret and the base Lookup class (https://github.com/ansible-collections/amazon.aws/issues/617). |
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.
Should we have backported a breaking change?
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.
@tremble I thought we could include this breaking change in 3.2.0. What do you suggest to do? Do we want to revert it and include in 4.0.0 directly?
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.
Uh yes. I think it must be reverted from stable-3
. It was mentioned here already #618 (comment)
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.
@markuman Can I do it in this PR or do we need a separate one?
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.
Sorry, missed completely that comment.
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.
If possible I would give it a try.
git reset --hard aeba19a # commit before that merge
git cherry-pick 7297e31 c06d77c 42295a7 d9d5d0d # cherry pick what comes after
and push with force? But I've no idea if that's more a punk way and will result in merge conflicts?
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.
Ok, thanks. let me try.
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.
...plus rebuild docs and changelog.
naybe there is also a smoother "rebase" way.....
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.
I rebuilt docs, but I have to hard reset and do it from the beginning. It happened in the past the same thing with the docs. I am re-doing right now. I only used git revert commit_hash
0755620
to
4edd684
Compare
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.
The changes to plugins/lookup/aws_ssm.py and tests/unit/plugins/lookup/test_aws_ssm.py don't seem to have been successfully reverted (we shouldn't have python changes in a prep PR - I might just be misunderstanding what's happening in #764 though).
@jillr Do we want to revert the changes in this PR or should I re-open #764 and merge first that one and then rebase this one? I am reverting the change in this prep PR at the moment. |
I re-opened this one and will do the revert directly here #764 instead of having it in the same prep PR. |
Yep, let's sort out the overall status of the stable-3 branch first and then rebase this PR for docs and changelog only |
Run add_docs, generate changelog Signed-off-by: Alina Buzachis <[email protected]>
4edd684
to
81367c3
Compare
Build succeeded.
|
regate |
Build succeeded (gate pipeline).
|
a27a3fa
into
ansible-collections:stable-3
…_password ec2_win_password - migrate to boto3 SUMMARY Migrate ec2_win_password to boto3 ISSUE TYPE Feature Pull Request COMPONENT NAME ec2_win_password ADDITIONAL INFORMATION While there are no tests for this module, there's only a single boto call to update boto2 documentation of call: http://boto.cloudhackers.com/en/latest/ref/ec2.html#boto.ec2.connection.EC2Connection.get_password_data boto3 documentation of call: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2.html#EC2.Client.get_password_data Reviewed-by: Rick Mendes <None> Reviewed-by: None <None> Reviewed-by: Alina Buzachis <None>
…_password ec2_win_password - migrate to boto3 SUMMARY Migrate ec2_win_password to boto3 ISSUE TYPE Feature Pull Request COMPONENT NAME ec2_win_password ADDITIONAL INFORMATION While there are no tests for this module, there's only a single boto call to update boto2 documentation of call: http://boto.cloudhackers.com/en/latest/ref/ec2.html#boto.ec2.connection.EC2Connection.get_password_data boto3 documentation of call: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2.html#EC2.Client.get_password_data Reviewed-by: Rick Mendes <None> Reviewed-by: None <None> Reviewed-by: Alina Buzachis <None>
SUMMARY
Run add_docs, generate changelog
ISSUE TYPE