-
Notifications
You must be signed in to change notification settings - Fork 3
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
Seqerakit docs port #296
base: master
Are you sure you want to change the base?
Seqerakit docs port #296
Conversation
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Llewellyn vd Berg <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some feedback about formatting which we'll apply across other developer docs if we're all in agreement.
platform_versioned_docs/version-24.1/seqerakit/yaml-configuration.mdx
Outdated
Show resolved
Hide resolved
platform_versioned_docs/version-24.1/seqerakit/installation.mdx
Outdated
Show resolved
Hide resolved
…ion.mdx Co-authored-by: Justine Geffen <[email protected]> Signed-off-by: Llewellyn vd Berg <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome work, thank you so much!
I've added two small comments. I wouldn't consider either of these blocking. |
@llewellyn-sl, the recognized terminal highlight styles are in
|
|
||
### Specify targets | ||
|
||
When using a YAML file as input that defines multiple resources, use the `--targets` flag to specify which resources to create. This flag accepts a comma-separated list of resource names. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it worth providing the list of possible resource names to be created via YAML config? I've been meaning to add this to the main README as well.
When using a YAML file as input that defines multiple resources, use the `--targets` flag to specify which resources to create. This flag accepts a comma-separated list of resource names. | |
When using a YAML file as input that defines multiple resources, use the `--targets` flag to specify which resources to create. This flag accepts a comma-separated list of resource names. | |
Supported resource names include: | |
- actions | |
- compute-envs | |
- credentials | |
- datasets | |
- labels | |
- launch | |
- members | |
- organizations | |
- participants | |
- pipelines | |
- secrets | |
- teams | |
- workspaces | |
seqerakit test.yml --targets pipelines | ||
``` | ||
|
||
This will process only the pipelines block from the YAML file and ignore `workspaces` and `compute-envs`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will process only the pipelines block from the YAML file and ignore `workspaces` and `compute-envs`. | |
This will process only the pipelines block from the YAML file and ignore creation of `workspaces` and `compute-envs`. |
|
||
Seqerakit has three dependencies: | ||
|
||
1. [Seqera Platform CLI (`>=0.9.2`)](https://github.com/seqeralabs/tower-cli/releases) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wondering if we should bump the minimum version to v0.10.1 here and in the main docs to avoid issues with pipeline name matching and reflection config errors reported by java, amongst other things.
|
||
### Configuration | ||
|
||
Create a [Seqera](https://cloud.seqera.io/) access token via **Your Tokens** in the user menu. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Create a [Seqera](https://cloud.seqera.io/) access token via **Your Tokens** in the user menu. | |
Create a [Seqera Platform](https://cloud.seqera.io/tokens) access token via **Your Tokens** in the user menu. |
- Using file path: | ||
|
||
```shell-session | ||
seqerakit /path/to/file.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't want to be overly pedantic as us SciDev's are guilty of this as well but should we decide on whether we want to use .yaml
or .yml
? Seems like we should standardize on .yaml
.
Customize YAML configuration templates to use in `seqerakit` commands to create, update, or delete Seqera resources. Create or delete multiple resources with a single command by combining them into a single configuration file. | ||
|
||
To use the templates on this page: | ||
1. Copy the template text or download the YML files you need. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1. Copy the template text or download the YML files you need. | |
1. Copy the template text or download the YAML files you need. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comment above.
|
||
For every entity defined in your YAML file, specify `overwrite: True` to overwrite any existing Seqera entities of the same name. | ||
|
||
Seqerakit will first check to see if the name of the entity exists. If so, it will invoke a `tw <subcommand> delete` command before attempting to create it based on the options defined in the YAML file. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seqerakit will first check to see if the name of the entity exists. If so, it will invoke a `tw <subcommand> delete` command before attempting to create it based on the options defined in the YAML file. | |
Seqerakit will first check to see if the name of the entity exists. If so, it will invoke a `tw <entity> delete` command before attempting to create it based on the options defined in the YAML file. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've found that users got quite confused when referring to the CLI calls made under the hood with <subcommand>
versus <resource>
or <entity>
.
@netlify /platform/24.1/seqerakit/installation
Ports and simplifies the Seqerakit docs into Platform Developer Tools.
TODO: