Additional / Custom Default ENV Variables for all pipes (workspace)

Hi,  As a pipe developer it would be nice to have a more elegant way to pass variables, in particular secrets, to pipes. Currently users can setup repo level or workspace level variables, but need to explicitly send them down to pipes.  It would be great if at a pipe level, and/or at a variable setup level, you could mark a variable as "always", which would mean that user defined variable acts like the other default Bitbucket variables (eg build number), so every step gets it, even if the pipe user does not send it down using the variables in the specific pipe step.  This will vastly simplify the users of pipes and prevent a lot of duplicative code in the pipeline yml files eg:  
 
AWS_DEFAULT_REGION: $COMMON_AWS_REGION
AWS_SECRET_ACCESS_KEY: $COMMON_AWS_SECRET_ACCESS_KEY
AWS_ACCESS_KEY_ID: $COMMON_AWS_ACCESS_KEY_ID