feat(studios): extend studio commands with support for configuration from git repository#642
Open
georgi-seqera wants to merge 1 commit into
Open
feat(studios): extend studio commands with support for configuration from git repository#642georgi-seqera wants to merge 1 commit into
georgi-seqera wants to merge 1 commit into
Conversation
…from git repository
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Configuring studios via Git repository config and studio configuration enhancements
This PR adds support for Git repository studio config as the headline feature, alongside several studio configuration enhancements across the
add,start, andupdatecommands.Main change: Git-backed studio configuration
Studios can now be created from a Git repository via
-u/--url, with an optional--revision(branch, tag, or commit). When a repository is provided,-t/--templatebecomes optional, since the remote repository may define the template itself.Other enhancements
Environment variables — set env vars with repeatable
-e/--env KEY=valuepairs (available onadd,start, andupdate).Spot instances — launch on spot via
--spot(onaddandstart). Note: whether spot instances are supported can depend on the chosen underlying compute environment where the studio is launched.SSH connectivity — enable SSH with
--ssh(onadd,start, andupdate); SSH host/port/command are shown in the studio view.Change compute environment on update — move a stopped studio to a compatible CE with
-c/--compute-env. If the target CE is incompatible, the CLI lists the compatible ones.Richer studio view — the studio view now also shows Private, Lifespan, SSH details, and environment variables.
Command examples
Add a template-based studio
Add a Git-backed studio (template optional)
Add on spot instances with SSH enabled
Start a studio with overrides
Update SSH connectivity
Move a stopped studio to a compatible compute environment