podman_link: environment variable changes for version 3.3.2

acute commented

2025-12-01 13:50:29 +00:00

Owner

BRIDGE_SIGNAL_AUTO_GROUPS - boolean - for bridge-worker
SIGNAL_AUTO_GROUP_NAME_TEMPLATE - string - for bridge worker
FORMSTACK_SHARED_SECRET - string - for link, bridge_worker
FORMSTACK_BRIDGE_MAPPING - json - for link, bridge_worker

By default these are optional.

ZAMMAD_API_TOKEN is also needed for bridge_worker if formstack functionality is needed.

BRIDGE_SIGNAL_AUTO_GROUPS - boolean - for bridge-worker SIGNAL_AUTO_GROUP_NAME_TEMPLATE - string - for bridge worker FORMSTACK_SHARED_SECRET - string - for link, bridge_worker FORMSTACK_BRIDGE_MAPPING - json - for link, bridge_worker By default these are optional. - ZAMMAD_API_TOKEN is also needed for bridge_worker if formstack functionality is needed.

irl added this to the (deleted) project 2025-12-21 18:10:46 +00:00

irl changed title from ~~Environment variable changes for version 3.3.2~~ to podman_link: environment variable changes for version 3.3.2

2025-12-22 09:59:57 +00:00

irl commented

2025-12-22 10:00:21 +00:00

Owner

@acute What is the actual task here? Do these need to be added to the zammad.env file?

irl commented

2025-12-22 10:02:13 +00:00

Owner

BRIDGE_SIGNAL_AUTO_GROUPS - boolean - for bridge-worker

Is this an "enable" flag?

SIGNAL_AUTO_GROUP_NAME_TEMPLATE - string - for bridge worker

What does this do? Where does it come from? What does it look like?

FORMSTACK_SHARED_SECRET - string - for link, bridge_worker

Where does this come from? What does it look like?

FORMSTACK_BRIDGE_MAPPING - json - for link, bridge_worker

What does this look like? Can we make the JSON ourselves out of a nice YAML dictionary in the variables?

By default these are optional.

* ZAMMAD_API_TOKEN is also needed for bridge_worker if formstack functionality is needed.

Same scope as Link needs or is it a different token?

> BRIDGE_SIGNAL_AUTO_GROUPS - boolean - for bridge-worker Is this an "enable" flag? > SIGNAL_AUTO_GROUP_NAME_TEMPLATE - string - for bridge worker What does this do? Where does it come from? What does it look like? > FORMSTACK_SHARED_SECRET - string - for link, bridge_worker Where does this come from? What does it look like? > FORMSTACK_BRIDGE_MAPPING - json - for link, bridge_worker What does this look like? Can we make the JSON ourselves out of a nice YAML dictionary in the variables? > > By default these are optional. > > * ZAMMAD_API_TOKEN is also needed for bridge_worker if formstack functionality is needed. Same scope as Link needs or is it a different token?

irl added this to the Link project 2025-12-22 10:13:08 +00:00

irl added the

enhancement

label 2025-12-22 10:16:39 +00:00

acute commented

2025-12-22 16:17:38 +00:00

Author

Owner

@irl wrote in #2 (comment):

BRIDGE_SIGNAL_AUTO_GROUPS - boolean - for bridge-worker

Is this an "enable" flag?

Yes - if enabled any incoming message makes the message into its own signal group and add the user and the helpdesk to it.

SIGNAL_AUTO_GROUP_NAME_TEMPLATE - string - for bridge worker

What does this do? Where does it come from? What does it look like?

Determines the name of the support group that the user gets added to in Signal. The user sees this as the Signal group name. It can be something like "helpdesk org Support", e.g. SR2 Support

FORMSTACK_SHARED_SECRET - string - for link, bridge_worker

Where does this come from? What does it look like?

generate it with pwgen, it's not necessary if the helpdesk isn't receiving support tickets via the API with formstack.

FORMSTACK_BRIDGE_MAPPING - json - for link, bridge_worker

What does this look like? Can we make the JSON ourselves out of a nice YAML dictionary in the variables?

I need to take a look.

By default these are optional.
* ZAMMAD_API_TOKEN is also needed for bridge_worker if formstack functionality is needed.
Same scope as Link needs or is it a different token?

The same one is used for both in the current model, although Darren says this can be changed. I have only ever managed to make it work with full permissions where formstack functionality is needed.

@irl wrote in https://guardianproject.dev/sr2/ansible-collection-apps/issues/2#issuecomment-136: > > BRIDGE_SIGNAL_AUTO_GROUPS - boolean - for bridge-worker > > Is this an "enable" flag? Yes - if enabled any incoming message makes the message into its own signal group and add the user and the helpdesk to it. > > > SIGNAL_AUTO_GROUP_NAME_TEMPLATE - string - for bridge worker > > What does this do? Where does it come from? What does it look like? Determines the name of the support group that the user gets added to in Signal. The user sees this as the Signal group name. It can be something like "helpdesk org Support", e.g. SR2 Support > > > FORMSTACK_SHARED_SECRET - string - for link, bridge_worker > > Where does this come from? What does it look like? generate it with pwgen, it's not necessary if the helpdesk isn't receiving support tickets via the API with formstack. > > > FORMSTACK_BRIDGE_MAPPING - json - for link, bridge_worker > > What does this look like? Can we make the JSON ourselves out of a nice YAML dictionary in the variables? I need to take a look. > > > By default these are optional. > > ``` > > * ZAMMAD_API_TOKEN is also needed for bridge_worker if formstack functionality is needed. > > ``` > > Same scope as Link needs or is it a different token? The same one is used for both in the current model, although Darren says this can be changed. I have only ever managed to make it work with full permissions where formstack functionality is needed.

Rows
Columns

podman_link: environment variable changes for version 3.3.2 #2