You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when using custom templates in the CircleCI Slack Orb, users need to manually handle the export of environment variables to customize the template fields. This process can be cumbersome and error-prone.
Maybe we could introduce an environment key under the slack/notify job where users can define environment variables directly within the CircleCI configuration. These variables would then be automatically available within the custom Slack templates, reducing the need for manual export steps.
Examples:
- slack/notify:
channel: some-channel
branch_pattern: main
template: basic_fail_2
environment:
FAILURE_MESSAGE: "Please take care of this issue ${SELECTED_VOLUNTEER}!"
Thanks!
The text was updated successfully, but these errors were encountered:
Describe Request:
Currently, when using custom templates in the CircleCI Slack Orb, users need to manually handle the export of environment variables to customize the template fields. This process can be cumbersome and error-prone.
Maybe we could introduce an environment key under the slack/notify job where users can define environment variables directly within the CircleCI configuration. These variables would then be automatically available within the custom Slack templates, reducing the need for manual export steps.
Examples:
Thanks!
The text was updated successfully, but these errors were encountered: