Skip to content

Custom environment options #48

Open
@silvertech-daniel

Description

@silvertech-daniel

I want to use this but my understanding from

`--environment=${deployToProduction ? "production" : "preview"}`,
is that there is no corresponding option to ensure that the vercel pull environment is the same as the target.

I think there should there be 4 variables (production, environment, pullEnvironment, and target):

  • with production treated as a shortcut to set environment to "production"
    • throw an error if production and any of the other variables are set at the same time
  • pullEnvironment/target default to environment
  • --prod set if target resolves to "production"

The interactions between this task's options and the vercel cli's options are confusing to me, so let me know if this doesn't make sense.

Extracted into a new issue from #46 (comment)

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