Add changelog for profile becoming mutually exclusive with other access tokens #1155
Conversation
tremble
added
the
do_not_backport
ansibullbot
added
community_review
feature
|
Build succeeded. ❌ ansible-galaxy-importer FAILURE in 4m 48s (non-voting) |
|
Build succeeded (gate pipeline). ❌ ansible-galaxy-importer FAILURE in 4m 51s (non-voting) |
Docs Build 📝Thank you for contribution!✨ This PR has been merged and your docs changes will be incorporated when they are next published. |
…aws in 5.0.0 (ansible-collections#1155) Update version_added information for modules which migrate to amazon.aws in 5.0.0 SUMMARY Felix has pointed out in IRC/Matrix that for modules which migrated to amazon.aws it can be a little confusing when you try to look back in logs to find exactly what needs to be installed for a feature (installing amazon.aws.4.3.0 doesn't guarantee that community.aws 4.x is installed) Update the main 'version_added' to match the version that the modules were moved to amazon.aws, and add the version_added_collection for existing new features. ISSUE TYPE Docs Pull Request COMPONENT NAME various modules ADDITIONAL INFORMATION Scope is currently limited to the 5.0.0 migrations, to simplify backports. If accepted I'll cleanup the 4.0.0 and 2.0.0 modules too. Reviewed-by: Felix Fontein <[email protected]>
Depends-On: ansible-collections/amazon.aws#834
SUMMARY
amazon.aws/834 made profile mutually exclusive with the other access token parameters, add a changelog fragment to community.aws since it's a significant change that also affects this collection
ISSUE TYPE
COMPONENT NAME
changelogs/fragments/151-profile-mutually-exclusive.yml
ADDITIONAL INFORMATION