MetaCell / MetaCell/cloud-harness
When using a custom image for on_exit_notify of a workflow queue and payload should not be mandatory
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 5
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 3
Description
When using a custom image for the on_exit_notify I would like to not need to specify the queue and payload parameters since those might not be needed for my custom scenario
https://github.com/MetaCell/cloud-harness/blame/develop/libraries/cloudharness-common/cloudharness/workflows/operations.py#L171
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
Read libraries/cloudharness-common/cloudharness/workflows/operations.py at the linked on_exit_notify implementation. Trace how queue and payload are currently required, then verify that a custom image can omit both while existing queue and payload behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100