New projects are not given a unique alias
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the project deploy --new --name and openfn deploy --new --name copy flows from the issue, first on the default alias and then against the same domain. Inspect how deployment aliases and the local project@domain.yaml state are tracked; done means the new project has a unique alias and the original project remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100