Skip to content
This repository was archived by the owner on Mar 14, 2023. It is now read-only.
This repository was archived by the owner on Mar 14, 2023. It is now read-only.

Allow CLI environment to be optional / add default environment #38

@timkelty

Description

@timkelty

Making this issue here to brainstorm the best way to handle this.

Here's what I'm currently thinking:

  • Allow setting a "default" environment statically in shipit.initConfig.
    • Environment set in the CLI command would override.
    • This would allow for workflows where certain branches deploy to certain environments by default (e.g. masterproduction, developmentdevelopment). The user could set the environment in shipit.initConfig to a function that parsed your current git branch and returned the matching environement. Of course, they could always override it by passing an environment in the CLI
  • If no environment set in either CLI or shipit.initConfig, trigger an inquirer choices prompt.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions