Validate workflow `id` value somewhere
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start at the workflow upsert request that builds the /tasks/workflows/{id} URL and inspect how IDs are accepted there. Reproduce the issue with microsoft/landsat; done means the slash is safely handled or the ID is rejected with clear validation, with coverage for this case.
Written by the indexing model from the issue text.
Description
Run into "bug" when I submitted a workflow with the id microsoft/landsat.
Error upserting workflow!
404 Client Error: Not Found for url: https://pctaskstest-staging.azure-api.net/tasks/workflows/microsoft/landsat
presumably the / needs to be url-encoded or disallowed.
- Dominant language
- Python
- Stars
- 43
- Forks
- 19
- Avg merge
- 1h 23m
- Merged PRs (30d)
- 1
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.
More from microsoft/planetary-computer-tasks
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Add workflow linter Openenhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in microsoft/planetary-computer-tasks
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100