[PR #5019/3fe9592c backport][stable-4] Slack: Add support for (some) groups #5043
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a backport of PR #5019 as merged into main (3fe9592).
SUMMARY
Some of the older private channels in the workspace I'm working in have channel ID's starting with
G0
andGF
and this resulted to false positivechannel_not_found
errors.I've added these prefixes to the list to maintain as much backwards compatibility as possible.
Ideally the auto-prefix of the channel name with
#
is dropped entirely, given the Channel ID's have become more dominant in the Slack API over the past years.ISSUE TYPE
COMPONENT NAME
Slack notification module
ADDITIONAL INFORMATION
This ansible task will trigger the "channel_not_found" error, because this module erroneously prefixes the channel id with
#
: