Allow updating custom AMI for the Head Node
Open
3.x
enhancement
Feature Request
- Dominant language
- Python
- Stars
- 888
- Forks
- 314
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
Currently a cluster can't be updated to use a different `custom_ami` than it was created with. For deployments needing long installs of additional software, it is much more convenient to generate pre-baked images, given that the only workarounds are either deleting & recreating a cluster or deploying to the shared fs (which may not be accessible from the image's CI).
Contributor guide
Assessment
This issue has not been assessed yet.