mirror of
https://github.com/ansible-collections/community.general.git
synced 2025-07-26 22:51:23 -07:00
Added some clarity on the token confusion. (#19473)
This commit is contained in:
parent
8f97ddd98a
commit
0568adc272
1 changed files with 7 additions and 1 deletions
|
@ -48,7 +48,13 @@ options:
|
||||||
are in the new format then slack will ignore any value of domain. If
|
are in the new format then slack will ignore any value of domain. If
|
||||||
the token is in the old format the domain is required. Ansible has no
|
the token is in the old format the domain is required. Ansible has no
|
||||||
control of when slack will get rid of the old API. When slack does
|
control of when slack will get rid of the old API. When slack does
|
||||||
that the old format will stop working.
|
that the old format will stop working. ** Please keep in mind the tokens
|
||||||
|
are not the API tokens but are the webhook tokens. In slack these are
|
||||||
|
found in the webhook URL which are obtained under the apps and integrations.
|
||||||
|
The incoming webhooks can be added in that area. In some cases this may
|
||||||
|
be locked by your Slack admin and you must request access. It is there
|
||||||
|
that the incoming webhooks can be added. The key is on the end of the
|
||||||
|
URL given to you in that section.
|
||||||
required: true
|
required: true
|
||||||
msg:
|
msg:
|
||||||
description:
|
description:
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue