galaxyproject / galaxyproject/cloudlaunch
[Admin Bug] Launch configs bug with no default cloud set
Open
- Dominant language
- Python
- Stars
- 42
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
Launch configs don't propagate to VM when the application doesn't have a default cloud set
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how launch configurations are propagated when an application has no default cloud, using the issue's reproduction condition. Reproduce the case with an application lacking a default cloud and verify that its launch configuration reaches the VM; the payload names no files or tests to begin with.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100