Skip to content

New projects are not given a unique alias #1523

Description

@josephjclark

When you do project deploy --new --name, we do not seem to create a new alias. So basically the new project will overwrite the original oroject

issue as bookmark to investigate

  • checkout a project (make sure it's on the default alias)
  • re-deploy it openfn deploy --new --name copy
  • your checked-out state is now the new copy (is this right? idk tbh - probably?)
  • there is only one local project@domain.yaml file and it tracks the clone, not the original

This isn't a problem when deploying to a different endpoint: but if posting to the same domain it's not good.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    • Status
      New Issues

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions