Exclude environments not part of deply

[Morten Seifert (mortenseifert)]

Idea Description

When running CI/CD pipeline all configured environments are included in the deply matrix.

At our company, the most common configuration is to have two environments configured for a customer

• Production
• Sandbox

When running CI/CD both environments are examined and the Production environment is skipped, because it is a production environment. Deployment to this environment is handled by running different action. This is all good.

However, in GitHub it looks like the artifact has been published to the Production environment, which is really misleading. By excluding the Production environment from the available environments in DetermineDeploymentEnvironments.ps1 would show the deployment history more correct.

I understand that the action would need to authenticate with the environment to determine the environment type.

Contribution (Optional)

• I would be open to contributing to this idea (implementation, documentation, testing, etc.)