Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Environment Targets 🌍 #44

Merged
merged 10 commits into from
Jun 27, 2022
Merged

Environment Targets 🌍 #44

merged 10 commits into from
Jun 27, 2022

Conversation

GrantBirki
Copy link
Member

@GrantBirki GrantBirki commented Jun 27, 2022

Environment Targets 🌍

With this Action (new feature), you can also choose the environment you wish to deploy to. This is useful if you have multiple environments and want to deploy to a specific environment.

This can be achieved with the environment_targets input

With this option, you can specify a comma separated list of environments that you can deploy to besides just the default with .deploy

The defaults that are used are: production,development,staging. However, you can configure this to be whatever you like!

To use a deployment with a specific environment, you would invoke your commands like so:

  • .deploy production
  • .deploy to production
  • .deploy to <environment>

This also works with noop commands as well

  • .deploy noop production
  • .deploy noop to production
  • .deploy noop to <environment>

Note: If no matching targets are found, then the default is used

@GrantBirki GrantBirki added the enhancement New feature or request label Jun 27, 2022
@GrantBirki GrantBirki merged commit fc09997 into main Jun 27, 2022
@GrantBirki GrantBirki deleted the environment-targets branch June 27, 2022 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant