We'd like the ability to set global environment variables that persist across Script Steps. Currently, Harness supports this for CI stages and Run steps where you can set Stage/Pipeline variables and have them added as env variables but, for Script Steps in Custom and CDS stages, this does not work.

Part of our requirement is to use elevated AWS permissions during the pipeline execution and use lower AWS permissions when a pipeline is not running. To this extent, we need to persist the AWS Credential env vars across Script Steps.