Allow Shell Script Step to Automatically Use Connector Permissions
G
Garnet Cricket
Currently, the Shell Script step does not automatically inherit or use permissions associated with a configured connector. Users must manually handle authentication, for example by writing scripts to assume roles when using OIDC.
Problem Statement:
This creates additional overhead and inconsistency compared to other steps that already leverage connector credentials natively. Users expect the Shell Script step to seamlessly use the same connector permissions without needing to manually replicate the authentication logic.
Requested Feature:
Enable the Shell Script step to optionally use connector credentials automatically (similar to how other steps handle authentication). This could be implemented via a toggle or configuration field that allows users to select an existing connector for credential context.
Example Use Case:
- A user wants to run a script in an AWS environment using OIDC.
- Today, they must add logic in the script to assume the IAM role manually.
- With this feature, the step would automatically inherit the connector’s OIDC permissions, eliminating that extra scripting.
Log In