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.
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 orojectissue as bookmark to investigate
openfn deploy --new --name copyThis isn't a problem when deploying to a different endpoint: but if posting to the same domain it's not good.