Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add YAML editor for tools #1156

Closed
MoritzWeber0 opened this issue Nov 2, 2023 · 0 comments · Fixed by #1311
Closed

Add YAML editor for tools #1156

MoritzWeber0 opened this issue Nov 2, 2023 · 0 comments · Fixed by #1311
Assignees

Comments

@MoritzWeber0
Copy link
Member

MoritzWeber0 commented Nov 2, 2023

Instead of form fields in the frontend, we should configure the metadata for tools in a yaml editor.
Part of the initial YAML editor should be:

The YAML would shall look like:

name: Capella

persistent-sessions:
  - id: native-capella
    image: k3d-myregistry.localhost:12345/capella/remote:$version-latest
    name: Native Capella

provisioned-sessions: # optional key
  - image: k3d-myregistry.localhost:12345/capella/readonly:$version-latest
    id: native-capella # Must be unique in list of provisioned-sessions
    name: Native Capella

# Temporary solution until https://github.com/DSD-DBS/capella-collab-manager/pull/722 is merged.
# Optional key
backup-image: k3d-myregistry.localhost:12345/t4c/client/base:$version-latest

The largest changes are:

  • read-only sessions are renamed to provisioned sessions. This is required for Initialize training setup, spawn related sessions #1004.
  • Persistent sessions and provisioned sessions are now lists, meaning that a tool can define different images. This has to be considered during session spawning. The feature is required for Add description editor in the frontend #859.
  • Each session type can have it's custom name now -> A tool can named differently than what is displayed in the session creation component.

Depends on #1135.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

1 participant