enterprise-release: 26.1 Documentation#1303
Conversation
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
* docs: document GitHub App credentials and manifest flow Add a new GitHub App subsection to the Git integration overview for both cloud and enterprise docs, covering the credentials form (Access token vs GitHub App, with Create-and-add vs Add-preexisting), the manifest-based app creation flow, repository installation steps, and how to handle duplicate credentials. Includes the credentials form screenshot for the new GitHub App tab. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * docs: add GitHub manifest page screenshot Replace the second image placeholder with a screenshot of GitHub's "Create GitHub App" page showing the pre-filled manifest, in both cloud and enterprise docs. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * docs: add GitHub App installation screenshot Replace the third image placeholder with a screenshot of GitHub's App installation page showing repository selection, in both cloud and enterprise docs. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Update platform-cloud/docs/git/overview.md Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Update platform-cloud/docs/git/overview.md Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Update platform-cloud/docs/git/overview.md Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Update platform-cloud/docs/git/overview.md Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Update platform-cloud/docs/git/overview.md Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Update platform-cloud/docs/git/overview.md Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Update platform-cloud/docs/git/overview.md Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Update platform-cloud/docs/git/overview.md Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Update platform-cloud/docs/git/overview.md Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Update platform-cloud/docs/git/overview.md Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Update platform-cloud/docs/git/overview.md Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Update platform-cloud/docs/git/overview.md Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Apply suggestion from @christopher-hakkaart Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Apply suggestion from @christopher-hakkaart Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Apply suggestion from @christopher-hakkaart Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Apply suggestion from @christopher-hakkaart Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Apply suggestion from @christopher-hakkaart Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Apply suggestion from @christopher-hakkaart Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Apply suggestion from @christopher-hakkaart Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Apply suggestion from @christopher-hakkaart Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Removed cloud content --------- Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: Justine Geffen <justinegeffen@users.noreply.github.com> Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io>
Added v1 of release notes Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Added new features and improvements for Azure, AWS, and GCP compute environments, including credential support and configuration updates. Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Merge Azure/AWS/GCP sections into Compute environments, fix tense (6 items), correct product names (Studios, data link), move miscategorized bug fix, backtick code elements. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
49875cd to
eef54fd
Compare
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
* docs(seqera-ai): add Projects page for Enterprise Enterprise mirror of the Cloud Projects page. Documents how Seqera AI derives projects from Seqera Platform workspace labels prefixed with `project_`. Adapted from internal docs in seqeralabs/portal#865 for public-docs audience, with Enterprise-specific deployment note. - Add platform-enterprise_docs/seqera-ai/projects.md - Surface the page in the Enterprise Seqera AI landing page (index.md) - Register the page in the Enterprise sidebar Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Update platform-enterprise_docs/seqera-ai/projects.md Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Update platform-enterprise_docs/seqera-ai/index.md Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Update platform-enterprise_docs/seqera-ai/projects.md Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Update platform-enterprise_docs/seqera-ai/projects.md Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> * Update platform-enterprise_docs/seqera-ai/projects.md Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> --------- Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io>
…1372) * Update references to platform images in all docs pages * Update v24 docs for new harbor enterprise path * Add banners to v24+ for new image distribution endpoint
Added significant improvements to integration, troubleshooting, and management. Updated environment variables and made various enhancements to Studios and compute environments. Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
* Added upgrade notes for 26.1 * Update upgrade.md Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com> --------- Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
| @@ -1,28 +1,27 @@ | |||
| --- | |||
| title: "Upgrade deployment" | |||
There was a problem hiding this comment.
@bebosudo, @gavinelder, @swampie: please could you review this upgrade guide. Thanks!
| Description: > | ||
| Disable Data Explorer automatic cloud bucket retrieval per workspace. | ||
| Value: 'Example: `<workspace-id1>,<workspace-id2>`' | ||
| # TODO(26.1): not in platform repo's ENVIRONMENT-VARIABLES.md — verify still valid |
There was a problem hiding this comment.
@georgi-seqera, @weronikasosnowskaseqera, @t0randr: please could you review this file and let me know whether any additions should be removed or edited. Thanks!
| @@ -0,0 +1,36 @@ | |||
| --- | |||
| - | |||
| Environment variable: '`TOWER_AUDIT_LOG_V2_WRITE_MODE`' | |||
There was a problem hiding this comment.
@tcrespog: please could you review these env vars and edit/approve as needed. thanks!
| Description: > | ||
| Allow log and report files from Nextflow CLI runs (`-with-tower`) to be accessible in the Seqera UI. Run output files must be accessible to your Seqera workspace primary compute environment. | ||
| Value: 'Default: `false`' | ||
| # TODO(26.1): not in platform repo's ENVIRONMENT-VARIABLES.md — verify still valid |
There was a problem hiding this comment.
@swampie, please could you confirm this env var is still valid.
| Description: > | ||
| The maximum file size of the Platform backend log file. When this limit is reached, a new log file is created. | ||
| Value: | ||
| # TODO(26.1): not in platform repo's ENVIRONMENT-VARIABLES.md — verify still valid |
There was a problem hiding this comment.
@swampie: please could I confirm whether the two callouts here are accurate? Thanks!
| @@ -0,0 +1,36 @@ | |||
| --- | |||
| - | |||
There was a problem hiding this comment.
@jonmarti, could you take a look at these env vars and LMK if they're accurate. Thanks!
| - Exposed roles API endpoints in the OpenAPI specification. | ||
| - Added SSO domain-based redirect for the login guard. | ||
|
|
||
| ### Monitoring and observability |
There was a problem hiding this comment.
@llewellyn-sl, could you take a stab at a more consolidated/logical list? I meant to ask Andrew before he went on leave. Thanks!
…qeralabs/docs into enterprise-26.1-documentation
bebosudo
left a comment
There was a problem hiding this comment.
I'm making my review as in need for changes since the nextflow launcher container image name needs to be confirmed
| - Replace `redisson.*` references in `tower.yml` with `TOWER_REDIS_*`. | ||
|
|
||
| :::note | ||
| Set `TOWER_REDIS_*` values directly in the `tower.yml` or AWS Parameter Store entry (for example, `TOWER_REDIS_URL: redis://...`). |
There was a problem hiding this comment.
what does this sentence mean? Arent' TOWER_REDIS_ environment variables?
|
|
||
| ### AWS data lineage tracking via SQS (preview, AWS only)** | ||
|
|
||
| 26.1 introduces a preview of AWS data lineage tracking that depends on an Amazon SQS queue. This feature is AWS-only and disabled by default. If you plan to enable it, ensure your IAM policies grant the Seqera role the relevant SQS permissions in addition to the existing [Seqera IAM permissions](../compute-envs/aws-batch#iam-user-creation). |
There was a problem hiding this comment.
Is there a docs page that we can refer to? I don't see SQS permissions in the aws batch page.
Moreover, does it work with the AWS Cloud CE too?
There was a problem hiding this comment.
@robnewman, is this accurate or an hallucination?
There was a problem hiding this comment.
The main additional AWS permissions needed by the opt-in Lineage feature are listed and can be referred to here: https://docs.seqera.io/platform-cloud/data/data-lineage#additional-iam-permissions-required
These have been tested with both AWS Batch and AWS Cloud CE and both work
Extra context: the main thing is that the credentials used also need to have the iam:PutRolePolicy (which we currently list as needed for both Batch and Cloud CEs) to be able to update the CE instance roles with access to the lineage storage bucket dynamically at pipeline launch time.
If the AWS resources are manually created (not via Forge) then customers need to manually add the custom permissions on the instance roles themselves (also listed in the referenced doc)
| ## Nextflow launcher image | ||
|
|
||
| If you host your nf-launcher container image on a private image registry, copy the [nf-launcher image](https://quay.io/seqeralabs/nf-launcher:j17-24.04.4) to your private registry. Then update your `tower.env` with the launch container environment variable: | ||
| If you host your nf-launcher container image on a private image registry, copy the [nf-launcher image](https://quay.io/seqeralabs/nf-launcher:j17-25.10.x) *(confirm exact tag at release cut)* to your private registry. Then update your `tower.env` with the launch container environment variable: |
There was a problem hiding this comment.
| If you host your nf-launcher container image on a private image registry, copy the [nf-launcher image](https://quay.io/seqeralabs/nf-launcher:j17-25.10.x) *(confirm exact tag at release cut)* to your private registry. Then update your `tower.env` with the launch container environment variable: | |
| If you host your nf-launcher container image on a private image registry, copy the [nf-launcher image](https://quay.io/seqeralabs/nf-launcher:j17-25.10.x) *(TODO: confirm exact tag at release cut)* to your private registry. Then update your `tower.env` with the launch container environment variable: |
marking this with a TODO
let's keep this comment open for visibility, I'll also mark my review as needing changes
|
|
||
| :::caution | ||
| If you're using AWS Batch, you will need to [configure a custom job definition](./advanced-topics/custom-launch-container) and populate the `TOWER_LAUNCH_CONTAINER` with the job definition name instead. | ||
| If you're using AWS Batch, you will need to [configure a custom job definition](https://docs.seqera.io/platform-enterprise/enterprise/advanced-topics/custom-launch-container) and populate the `TOWER_LAUNCH_CONTAINER` with the job definition name instead. |
There was a problem hiding this comment.
why the absolute link which may break when we'll rename vNext to v26 and version it?
There was a problem hiding this comment.
That's Claude - I have changed the prompt to force relative links but it does get confused with the changelog which needs absolute links. Probably need two separate skills.
Co-authored-by: Alberto Chiusole <1922124+bebosudo@users.noreply.github.com> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Co-authored-by: Alberto Chiusole <1922124+bebosudo@users.noreply.github.com> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Co-authored-by: Alberto Chiusole <1922124+bebosudo@users.noreply.github.com> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Co-authored-by: Alberto Chiusole <1922124+bebosudo@users.noreply.github.com> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Co-authored-by: Alberto Chiusole <1922124+bebosudo@users.noreply.github.com> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Co-authored-by: Alberto Chiusole <1922124+bebosudo@users.noreply.github.com> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Co-authored-by: Alberto Chiusole <1922124+bebosudo@users.noreply.github.com> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Co-authored-by: Alberto Chiusole <1922124+bebosudo@users.noreply.github.com> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Co-authored-by: Alberto Chiusole <1922124+bebosudo@users.noreply.github.com> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Includes: