Codepipeline cloudformation missing EnvironemntVariables for Provider: Commands

You are correct that there is no direct provision for setting environment variables in the CloudFormation template for the Commands action in CodePipeline. The Commands action is designed to run shell commands in a virtual compute instance without creating a CodeBuild project, and it doesn't have a built-in way to specify environment variables in the CloudFormation template.

However, there are a few workarounds you can consider:

1. Use inline commands to set environment variables: You can set environment variables directly in your Commands section using shell commands. For example:

   Commands:
     - export MY_VAR=value
     - echo $MY_VAR
     - # rest of your commands

2. Use a script file: If you have multiple environment variables or complex setup, you can create a separate script file that sets up the environment variables and include it in your source artifacts. Then, you can execute this script as part of your Commands.

3. Use CodeBuild instead: If you need more complex environment variable management, consider using a CodeBuild project instead of the Commands action. CodeBuild provides more flexibility for setting environment variables, including the ability to use parameter store or secrets manager for sensitive values.

4. Use pipeline variables: If the environment variables you need are available as pipeline variables (like execution ID or commit ID), you can reference them directly in your commands using the variable syntax, e.g., #{codepipeline.PipelineExecutionId}.

Remember that while these workarounds can help, they may not provide the same level of flexibility and security as setting environment variables through the console. If you require more robust environment variable management, using a CodeBuild project might be a better option.
Sources
Commands action reference - AWS CodePipeline
Working with variables - AWS CodePipeline