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
In the old ruby-based r10k webhook there was a configuration option to provide a command which would dynamically determine the environment prefix for a particular branch at runtime, rather than having a single static prefix.
Are there plans to add this functionality to the Go implementation?
We run a multi-tenant environment, and have a script to prefix environments based on the source repository the request originates from, so that each tenant can have a production branch in their own control repo, which gets mapped to tenantname_production when it is run through r10k.
This feature is vitally important to our existing workflow, so we're currently unable to use the Go implementation until it is added.
The text was updated successfully, but these errors were encountered:
This currently is not supported due to some problems with the way Go's os/exec library can have issues if you try and add too many parameters to the command string. I can look into it again, but it's likely going to have to wait until we migrated to utilizing and updating https://github.com/xorpaul/g10k
In the old ruby-based r10k webhook there was a configuration option to provide a command which would dynamically determine the environment prefix for a particular branch at runtime, rather than having a single static prefix.
Are there plans to add this functionality to the Go implementation?
We run a multi-tenant environment, and have a script to prefix environments based on the source repository the request originates from, so that each tenant can have a
production
branch in their own control repo, which gets mapped totenantname_production
when it is run through r10k.This feature is vitally important to our existing workflow, so we're currently unable to use the Go implementation until it is added.
The text was updated successfully, but these errors were encountered: