This site is in read only mode. Please continue to browse, but replying, likes, and other actions are disabled for now.

⚠️ We've moved!

Hi there!

To reduce project dependency on 3rd party paid services the StackStorm TSC has decided to move the Q/A from this forum to Github Discussions. This will make user experience better integrated with the native Github flow, as well as the questions closer to the community where they can provide answers.

Use 🔗 Github Discussions to ask your questions.

Pack configs different hosts/credentials

Hi, I hoping someone can point me in the right direction as i have done some searches.

I am looking at using Stackstorm as our automation platform and while performing some trials. I have noticed that there appears to be a lack of ability to target multiple environments.

This seems to be an issue with the majority of packs i have used. The packs require you to config the target hosts and credentials within thier config file. Therefore if you want to target a different host or use different credentials for different rules/workflows impossible.

My question is, is it possible to override the config file at runtime based on inputs or is this something that has to be designed into the pack actions?

Thank you in advance.


Can you explain a bit more why you expect to need to target different hosts on-the-fly, or give me an example or two?

Some actions in some packs may allow users to override the defaults configured in the pack config file, however…

I’m having a difficult time imagining a Jira server, or a Gitlab instance, or a Sensu master jumping around frequently, for example. Usually you would configure StackStorm to connect to one (or more) instances of a service and then users could run actions/workflows on those instances. Or you would run chatops with a single chat provider.

If you need to segregate StackStorm in different environments, instead of targeting hosts at runtime, you can run multiple instances of StackStorm - one in each separate environment. The open source license allows you to run as many StackStorm instances as you wish across all of your environments.

A notable exception to this is the core.remote action - that can (obviously) run commands on different remote hosts that are specified at runtime.

Hope this helps!

Hi Blag

To give an example,
We are currently doing managed monitoring for a number of clients. One of the tasks is when an alert is generated it gets processed. Then based on a ruleset a ticket is logged into the clients servicedesk software. At the moment we have a number of clients using Jira as an example.

The jira actions use a single config therefore my options are to modify the jira repo/create my own/run multiple instances of stackstorm for each client that uses Jira/ServiceNow(the pack has the same limitations).

Having a quick look at the AWS pack. The region and access id and key are in the config file and i can’t change them at runtime. Which will be limited to a single client per st2 instance.

So would it be fair to say, it looks to be a constraint to how stackstorm works and how packs a generally written?

I can see you can use the key value store for config entries. it would be nice if you could scope rules outside of system/user and then have configs pull from those scopes or something along those lines.

Thanks for your help


What you’re describing is usually a deficiency of the packs themselves. Most of the packs are maintained by community members and would LOVE contributions for enhancements like you’re describing!


@pdenning To answer your question directly: this is something that has to be designed into the pack actions themselves. And this does fundamentally shift the security model of StackStorm configs (more on this at the end). It is also not as easy or straightforward to implement securely as it might appear.

However, as Nick noted, the vast majority of packs would benefit greatly from this, it’s just that nobody has bothered to implement it. As I’m sure you’ve seen, there are quite a few packs in our official Exchange.

I can think of at least two different ways to implement this.

Method #1: Add specific, optional parameters to actions that override the values specified in the central pack config. You would have to do this for every action in every pack you want to use this way, and it would be difficult to force a consistent implementation across different packs (although we might be able to help you update packs in the Exchange, depending on our availability). This would allow pack authors to limit what options can be overridden (more on this later). For instance, actions in the Jira pack could allow ST2 users to specify their own jira_username and jira_password options that would override the default StackStorm config values. This basically would change the way the central pack config is treated, and would treat it as a collection of “default” values for each organization that is using StackStorm.

Method #2: Add a single config dictionary parameter to actions that overrides the entire central pack configuration. This could be implemented in fewer places than every action in every pack, but it would be slightly clunky for action users to use because they would need to know - a priori - what values to use for all values in the config dictionary. For example, actions in the Jira pack could rely on the following config values:

url: ...
username: ...
password: ...

But this runs into issues where a ST2 user may want to override username and password, but not override url. They would need to know what the “default” value is for url are in the central pack config, and if that value ever changed, each action execution would need to be updated to use the new url value.

Method #3: Allow users to override some central pack config values without having to override all config values. This sounds like a great solution, but it requires a lot more refactoring in ST2 itself than it might first appear. Consider the Jira host and port options above. This method would allow users to override username and password and let the ST2 admins specify the host and port values (which would be pulled from the central pack config).

However, this could extremely easily lead to security issues. A malicious user could override only the host parameter and point it to a server that they control. When they run that action, StackStorm would use the username and password values from the central pack config, and attempt to login to the malicious host. All they have to do is capture the credentials from the login attempt and they have the default values from the central pack config. And usually you would want those values to be for a Jira account that has a lot of permissions on Jira (eg: a Jira admin account). So any user could fairly painlessly capture admin credentials using this method.

The “proper” way to address this is to implement configuration inheritance in StackStorm itself, which, as the name would imply, could get very messy very quickly. Essentially, this would require support in configuration schemas for specifying configuration value dependencies. For example, if the url config value is overridden, the username and password values would need to be overridden as well, but poll_interval, project, and verify would not need to be explicitly overridden.

Here’s an example config schema:

    description: "URL of the JIRA instance (e.g. ````)"
    type: "string"
    secret: false
    required: true
    description: "Username if using the basic auth_method"
    type: "string"
    secret: false
    required: false
    override-with: url
    description: "Password if using the basic auth_method"
    type: "string"
    secret: true
    required: false
    override-with: url
    description: "Polling interval - default 30s"
    type: "integer"
    secret: false
    required: false
    default: 30
    description: "Project to be used as default for actions that don't require or allow a project"
    type: "string"
    secret: false
    required: true

That config schema would allow child configs to specify their own username and password parameters without needing to override url, but it would force them to specify their own username and password parameters if they specified their own url parameter.

This is definitely an advanced feature, and (as far as I know) would only be used by a small minority of StackStorm users/installations. Furthermore, because it requires a high degree of understanding, it would be easy for pack authors to incorrectly specify dependencies, or specify them in reverse order.

I’m not saying the third method would be rejected, I’m just trying to explain why this isn’t as simple as it may appear on the surface.

If you have PRs to add override parameters (a la method #1), I think we’d be happy to have them (just be judicious in what parameters you allow to be overridden).

PRs for method #2 would probably be the best payoff in terms of your investment, but I would recommend creating a PR for one pack and then getting the StackStorm team to review it, since it would be a little clunky from a StackStorm user perspective.

Implementing method #3 should be done with buy-in/coordination with the StackStorm team.

Note: The term “central pack config” is a phrase I made up in this post simply to differentiate it from an overridden config specified by a user when running an action. It does not appear in StackStorm documentation, and people outside of this discussion will not know what it means.

1 Like

Hi Blag

Thank you for your very concise reply.

At this stage and reading from your reply, if i was to look at forking and submit a PR. I would look at doing your recommendation of method 2.

IMO if they are to override the username/password they should override the url even if it is the same. That way the’ll maintain configuration control if the default is ever changed.

Another method i would like to propose and get your opinion. Instead of having it overridable from a user perspective.
Have configuration sets that a user could select from

Example in the config schema the endpoint details would be an object looking something along the lines of.

"endpoints": {
    "client1": {
        "url": "",
        "user": "username",
        "password": "password"
    "client2": {
        "url": "",
        "user": "username",
        "password": "password"
    "client3": {
        "url": "",
        "user": "username",
        "password": "password",
        "default": true

Now there would be an configuration string that would define which config to use. If there is only 1 option it would be used by default, if there is multiple options the one defined as default would be used as default.

I haven’t gone down the path of forking the packs within the exchange yet as it is still early days in product trials, however we do like the way stackstorm is performing and i’ll be looking at the Jira repo to begin with this week. As our dev and internal ticketing is currently jira.

If i am to start down this path, i would like to PR. therefore i would value input on the best approach so i can contribute them back into the community.

Thanks for all your advice so far.

Just to clarify - what you posted is the JSON representation of a YAML example config file (StackStorm pack config files are typically YAML files, not JSON, although JSON files can be interpreted by modern YAML parsers). A YAML config schema is different. StackStorm uses YAML representations of JSONSchema to describe what can be configured in pack config files. I hope I am making this more clear, but if not just take a look at those links until you understand what’s going on (and please feel free to ask more questions).

My boss pointed me to how the AWS CLI handles this - it has what it calls “profiles”. This is pretty much exactly what you are looking to implement. This allows StackStorm administrators to limit and control what config values users can use, which prevents at least account enumeration, password brute forcing, and credential disclosure attacks.

The easiest way to make sure you’re on the right track is to fork a pack, start developing your fork a bit, and create a PR to the original repository on GitHub, then ask us to review what you have developed. That will allow us ST2 engineers to leave comments as you go and give you our feedback early in your development cycle.

One thing I will point out before you start - the Jira pack has existing users with existing configuration files. If you can avoid forcing them to update them, that would be very very good. Remaining reverse compatible would also not force users with simpler use cases to overcomplicate their config files. So instead of explicitly creating a default profile, I would treat the existing config values as the default profile, and only add a profiles key that contains admin-controlled overrides. That’s a lot of prose words to describe it, so here’s an example potential config file for you:

url: ""
rsa_cert_file: "/home/vagrant/jira.pem"
auth_method: "oauth"
oauth_token: ""
oauth_secret: ""
consumer_key: ""
poll_interval: 30
project: "MY_PROJECT"
verify: True
# ^^^^ current users of the Jira pack will already have these config values,
#      so treat these values as the default profile

# You would add support for the profiles key below
# Each profile would override values from the "default" profile above
# Values that are not overridden should be pulled from the "default" profile values above
  jira-dev:  # profile name - this is what users will use to identify their configuration
    auth_method: oauth
    oauth_token: ...
    oauth_secret: ...
    consumer_key: ...
  slow-jira:  # this instance is on a tiny VM so don't poll too often
    auth_method: simple
    username: slow-admin
    password: slow-password
    poll_interval: 120  # Every 2 minutes

That config file only has an additional profiles key when compared to existing users’ config files, and new Jira pack users who only need a single profile can still have a clean looking config file.

A few more pointers when developing a pack: shamelessly copy from other packs as much as you can, and start it with/submit it to our Exchange Incubator.

Hi Blag

Thanks for that, I do understand that stackstorm doesnt use JSON and is infact yaml.
I apologies as i was using JSON to convey a data structure for a “profile” type model.

Personally i tend to find JSON better at showing a data structure then YAML.

I do appreciate the response and pointing out backwards compatibility and i will take that into account when presenting a PR.

Thinking along the lines of defaults. I might add another option called default_profile: where default if left blank it’ll choose the inline(current method) options or a profile name to use as the default/falls back to the inline options if it can not find the profile.

I have implemented multi profiles on the Jira pack. Appears to work pretty well for the actions.

However I am not sure how to go about implementing it for senors. As it appears you can’t pass variables to the sensor at runtime.

If so could you please point me in the direction on how to do so

@pdenning was this implemented onto the jira pack? If so what is used during an action to specify the profile to use ? @blag if you have any info maybe?

In the hopes to find that this thread went radio silent because it got fully implemented, I have exactly the same requirement. I have a workflow that leverages several different packs ( AWS, TerraForm, some custom packs we wrote, etc. ) and intend to be able to have the actions be able to select different target enclaves based on inputs passed in the API call to the workflow.

I thought there should be a “st2 action” to reconfigure a pack on-the-fly, but of course this would possible break things when multiple actions are running concurrently that would need different configurations.

At least for TerraForm I’ve found a workaround to write out a .tf file with the proper AWS access key and secret and region then passing that into the Terraform apply call, but this isn’t exactly ideal as it writes in plain text access credentials to a client enclave. We delete it when we’re done, but that’s still not the point.

I suppose another approach would be to write custom wrappers to the native tasks that add the credentials to the session create calls but that starts to get complicated…

Would love to hear that this was already solved.