Skip to main content

83 posts tagged with "seqera cloud"

View All Tags

Seqera Cloud v27.1.0_cycle80

Feature updates and improvements​

Compute environments​

  • Added search and pagination to the compute environments list.
  • Added subnet failover to AWS Cloud compute environments, with multi-select subnets in Basic mode.
  • Changed new Google Batch compute environments to require at least 3584 MiB of head job memory.

Pipelines​

  • Redesigned the Launchpad list as a table with a column for each pipeline's compute environment, and made the list the default layout on every screen size.

Monitoring​

  • Redesigned the Runs and All runs lists as tables with a header checkbox for selecting every run, and removed the run status stripes and the unused Optimization available flag.

Data lineage​

  • Renamed the lineage Bucket name setting to Storage location and added support for a bucket prefix.

Co-Scientist​

  • Added Auto-change sandbox and a default sandbox setting to an agent.
  • Redesigned the recent conversations menu as single-row items with compact relative times.
  • Added read, unread, and running indicators to agent sessions in the conversation history.

Service accounts​

  • Added client credentials to service accounts. An organization owner generates a client ID and secret on the service account's Authentication tab, and an external app uses them to sign in to Seqera as that service account.
  • Added a Client credentials card listing each secret with its status, last use, and expiry date, and a Client credentials column on the service accounts list.
  • Added secret lifetimes of 30, 90, 180, or 365 days, and a warning on a secret in its last 14 days.
  • Added Rotate and Revoke actions to each secret. A service account holds up to two active secrets, so you can put a new secret in place before revoking the old one.
  • Added a Generate a secret option to the new service account form, which shows the Secret generated dialog as soon as you create the account.
  • Added audit events for issuing, rotating, and revoking a service account secret.

General​

  • Added outbound request protection to data link downloads and S3-compatible storage endpoints.
  • Added outbound request protection to Kubernetes compute environment servers and SSH scheduler login hosts.
  • Added verification of the X-Hub-Signature-256 signature on GitHub webhook deliveries.

Bug fixes​

Compute environments​

  • Fixed AWS Batch Forge compute environment creation failing with an sts:AssumeRole access denied error before the new IAM roles had propagated.
  • Fixed a compute environment work directory ending in a slash writing to a different prefix from the same path without one.

Credentials​

  • Fixed a newly created AWS access key being saved as invalid before AWS had propagated it.

Studios​

  • Fixed a running Studio with no recent heartbeat being shown as stopped on some screens and running on others.
  • Fixed Studio checkpoints and data link mounts failing when the work directory bucket name contains an underscore.
  • Fixed the empty Studio SSH key state showing a hint about deleting a key.

Data Explorer​

  • Fixed a Google Cloud Storage folder listing duplicating its entries when the folder spans more than one page.

Actions​

  • Fixed a bucket event that could not be queued being acknowledged to Amazon SNS instead of retried.
  • Fixed a chained pipeline not starting when the pod handling its run state event stopped mid-delivery.
  • Fixed an action name containing an underscore being rejected as a duplicate of a similarly named action.
  • Fixed actions saved before September 2021 loading without their configuration.

Pipelines​

  • Fixed resuming or relaunching a run pre-filling the pipeline's resource labels instead of the run's own.
  • Fixed selecting a config profile on a shared pipeline failing with a permission error when the run uses a compute environment of the launching workspace.
  • Fixed the launch form listing Nextflow versions oldest first.
  • Fixed removing every label from a resource failing instead of clearing the labels.

Co-Scientist​

  • Fixed the agent sessions list resetting to 10 rows per page after a page change, and staying on a later page after a search.

Monitoring​

  • Fixed the runs list failing to load in workspaces with many runs.

Seqera Cloud v27.1.0_cycle79

Feature updates and improvements​

Studios​

  • Added recovery of a Studio's last checkpoint when it was not saved completely, with an option to undo the recovery.
  • Added starting a new Studio from a checkpoint that was not saved completely.
  • Changed the recommended Xpra Studio template to 6.5.4 and marked the previous 6.3.6 template as deprecated.

Compute environments​

  • Added Spot VMs to the worker pool of an Azure Batch Forge compute environment that uses separate head and worker pools. The head pool always uses dedicated VMs.
  • Added pinned instance types to an AWS Batch Forge work queue when Fusion Snapshots is enabled and Instance types is empty.
  • Renamed the Allowed S3 buckets field to Additional S3 buckets on AWS Batch, AWS Cloud, and Seqera Compute compute environments.
  • Clarified the AWS CLI path helper text on AWS Batch compute environments.

Credentials​

  • Added an optional repository path to the Registry server of a container registry credential, so a credential can be scoped to a single repository.
  • Changed new AWS credentials to start in Role mode on Seqera Cloud.
  • Redesigned the credentials list as a table with columns for name, ID, last updated, last activity, and status.

Secrets​

  • Redesigned the secrets list as a table with columns for name, last updated, and last activity.

Data Explorer​

  • Added creating an empty folder on AWS S3, Google Cloud Storage, and Azure Blob Storage data links, in Data Explorer and in the data picker of the launch form.

Service accounts​

  • Added Access and Authentication tabs to the service account details page.
  • Added a Studio SSH key to a service account, which an organization owner can view and delete from the Authentication tab.

Co-Scientist​

  • Replaced the sandbox chip above the chat message box with a sandbox label and a Download sandbox contents icon below it.
  • Redesigned the conversation history with Chats and Agent sessions tabs, organization groups, and search.

Monitoring​

  • Added pipelineId: to the search suggestions on the runs list.

General​

  • Added outbound request protection in enforcing mode, which refuses requests to Git servers and other destinations you supply that resolve to private or link-local addresses.
  • Removed the credentials of a request from a Git server redirect that changes host, port, or scheme.

Bug fixes​

Compute environments​

  • Fixed Azure Batch Forge pools keeping container storage on the managed OS disk, which failed tasks with ContainerInvalidSettings.
  • Fixed a running Azure Cloud run being marked as failed after a single head VM poll returned no power state.
  • Fixed a Google Cloud run whose head VM was already deleted ending as unknown with an empty error report instead of failed.
  • Fixed the duplicate compute environment page showing the copy name in place of a page title.
  • Fixed an AWS compute environment form keeping an AMI ID from the previous region after the region changed.
  • Fixed AWS Cloud reporting a failed setup script on instance types that have no instance store NVMe disks.
  • Fixed job submission stalling for other runs when a compute environment's SSH host accepted a connection but never responded.

Credentials​

  • Fixed a GitHub App credential authenticating as the wrong installation when the app is installed on more than one account.

Data Explorer​

  • Fixed adding an Azure data repository with invalid credentials reporting a bucket validation error instead of a credentials error.

Data lineage​

  • Fixed lineage links failing to resolve in large workspaces because the lookup of a record's run timed out.
  • Fixed lineage run and task links not opening in a new tab, and not supporting middle-click, cmd-click, or Copy link.

Monitoring​

  • Fixed the run details page keeping the previous run on screen after navigating to another run.
  • Fixed empty logs, empty log downloads, and a reports tab stuck on Reports are generating when a run's files cannot be read over SSH.

Pipelines​

  • Fixed launches failing with a Wave service connection error during a routine reconnect of the Wave pairing.
  • Fixed a launch that adds resource labels reporting a data error instead of naming the role limit.
  • Fixed a Git repository that Platform cannot reach reporting an unexpected error instead of naming the repository and the reason.

Agents​

  • Fixed an agent launch being reported as failed while the agent backend continued and queued the run.

Seqera Cloud v27.1.0_cycle78

Breaking changes​

Private Studios now admit only the users on their allowed users list, the creator included. A creator who is not on the list can still start, stop, edit, and delete the Studio, but cannot connect to it or use its checkpoints. Existing private Studios with no allowed users have their creator added; a Studio already shared with another user keeps its list, and its creator must be added to it to connect.

Feature updates and improvements​

Studios​

  • Removed the limit of one additional allowed user on a private Studio, through the API.
  • Added stopping a private Studio, and extending its lifespan from inside the session, for its allowed users.
  • Added checkpoint access for a private Studio's allowed users, covering reading a checkpoint, renaming it, and creating a Studio from it.
  • Added mounting a data link in a Studio when it is in one of the compute environment's allowed S3 buckets, even if it uses other credentials. Applies to AWS Batch, AWS Cloud, and Seqera Compute compute environments.

Compute environments​

  • Added an Allowed S3 buckets field to the Seqera Compute compute environment form for granting access to S3 buckets in your own AWS account.
  • Added a Bucket policy section to the Seqera Compute compute environment details page with the policy to apply to each allowed bucket.
  • Redesigned the compute environments list as a table with columns for name, ID, region, enabled features, last activity, and status.

Monitoring​

  • Changed the run timeline to sort processes in pipeline order by default.
  • Added a Sort processes menu to the run timeline, with Earliest started and Latest started options.
  • Added an Attempt label to retried task rows in the run timeline, and a retry count to each process row.

Co-Scientist​

  • Changed the label below a conversation title to name the organization instead of the workspace.

Agents​

  • Added agents: named, reusable sets of instructions that Co-Scientist runs on your behalf in a workspace. Anyone in the workspace can run an agent without rewriting its prompt.
  • Added a service account as the identity an agent runs under. An agent's work is attributed to that account rather than to the person who created it.
  • Added binding a workspace GitHub App credential to an agent for clone, commit, and push operations in place of the creator's personal access token. Each installation token the agent mints is recorded in the audit log.
  • Added a read-only view of a workspace-owned agent thread in the Co-Scientist drawer, with a Fork button that copies the thread into a personal chat.
  • Added stopping a running agent session.
  • Added automatic disabling of an agent when its service account leaves the workspace.

Actions​

  • Added three event sources to actions: Bucket event, which fires when a marker file arrives in or is removed from cloud storage, Schedule, which fires on a recurring cadence, and Pipeline run event, which fires when a run of a watched pipeline reaches a terminal state.
  • Added an agent Target to the three new event sources, which hands the event to an agent instead of launching a pipeline.
  • Added Daily, Weekly, and Custom schedule options for a scheduled action. A saved action keeps the timezone it was created in.
  • Added Details and Trigger history tabs to the action details page. Trigger history lists each firing of the action and the event payload behind it.
  • Added a View target control to an agent row in Trigger history that opens the agent's conversation in the Co-Scientist drawer.
  • Added editing a saved action's name, labels, marker file, and schedule.
  • Added a label to the runs an agent action starts.
  • Added an optional pipeline and version to the Target of a pipeline run event action.
  • Changed a chained action to skip the run it caused itself.

Service accounts​

  • Added editing a service account's name, description, and workspace access from a dialog on its details page.
  • Blocked removing or deleting a service account that is bound to an active agent.

Access control​

  • Added single sign-out for applications that sign in with Seqera. Signing out of one now ends your Seqera session too.

General​

  • Improved screen reader output by hiding decorative icons and naming the icons that carry meaning.

Bug fixes​

Compute environments​

  • Fixed a compute environment deletion blocked by running workflows or active Studio sessions reporting a generic error instead of naming them.
  • Fixed Azure Batch Forge autoscaling adding one node per queued task instead of filling each node's task slots. Compute environments created earlier keep the previous formula.

Credentials​

  • Fixed the Azure credentials forms accepting Batch and Blob Storage account names that Azure rejects.
  • Fixed a Git credential with a repository base URL applying to other accounts whose names begin with the same text.
  • Fixed a Git credential with a repository base URL being ignored for a pipeline referenced by a short owner/repo name.

Datasets​

  • Fixed the dataset details page showing no avatar for a creator whose avatar comes from their identity provider.

Monitoring​

  • Fixed the run Parameters Groovy view producing text that is not valid Nextflow configuration. The view is now Nextflow config and downloads as a .config file.
  • Fixed the run Parameters JSON view showing a tree with unquoted keys instead of the JSON that Copy and Download produce.

Pipelines​

  • Fixed the Launchpad Recently updated sort ordering only the pipelines on the current page.
  • Fixed a launch form staying invalid with no explanation when the pipeline schema contained a pattern the browser cannot compile.

Projects​

  • Fixed the resource dialog clipping its pagination controls.

General​

  • Fixed icons in disabled buttons rendering at low contrast instead of following the button's color.

Seqera Cloud v27.1.0_cycle77

Breaking changes​

Google credentials now accept only service account keys. Creating or updating a credential with a key of another type, a non-Google token URI, or a universe domain other than googleapis.com fails, and a stored credential that fails the same check becomes invalid at its next validation. Workload Identity Federation credentials are unchanged.

Feature updates and improvements​

Compute environments​

  • Added Fusion version and Fusion snapshots settings to the compute environment, pipeline, and launch forms.

Studios​

  • Added a capacity check that blocks a Studio when its AWS Batch compute environment is full, and reports a session waiting for resources.

Agents​

  • Renamed the agent Pause and Resume actions to Disable and Enable.

Co-Scientist​

  • Changed a new conversation to bill the organization of the workspace it starts from, rather than one inferred from the page.

Datasets​

  • Moved the datasets table to the comfortable layout, with taller rows and more space in each cell.
  • Added a View hint to the runs link on a dataset row.

Pipelines​

  • Added Nextflow 26.10.0 to the version catalog.

Data Explorer​

  • Added a specific error for a bucket the selected credentials cannot access, in place of a generic failure.
  • Moved the Data Explorer list from row cards to a headed table in the comfortable layout. Hidden now sits next to a repository's name, beside Public.

Bug fixes​

Compute environments​

  • Fixed a Google Cloud head VM staying up when its first self-delete was refused. It now retries for up to an hour.
  • Fixed an Azure Cloud run that ends before Nextflow reports its start giving no diagnosis. The error now points to the head's launcher output.
  • Fixed AWS Forge leaving s3:AbortMultipartUpload out of the policy it writes for the work directory bucket, where a failed or canceled multipart upload left incomplete parts behind. Compute environments created before this release keep their existing policy.
  • Fixed a Studio on a Google Cloud compute environment failing to pull a private container image from Artifact Registry or Container Registry. The head VM now authenticates to the registry with its own identity.

Pipelines​

  • Fixed the launch form leaving nested run parameters empty when a config profile set them.
  • Fixed a long version name misaligning the columns of the Launchpad list.
  • Fixed editing a pipeline's Seqera Platform schema failing with an "already exists" error when the schema declares an $id.

Co-Scientist​

  • Fixed a conversation showing no feedback while its transcript loaded.

Agents​

  • Fixed a failed agents list showing the "No agents configured yet" empty state instead of an error.

Projects​

  • Fixed the project edit form omitting project pipelines that sorted past the first page.

Data Explorer​

  • Fixed the data picker offering Upload to users without permission to upload.

Credits​

  • Fixed storage and network usage not being priced, so it never drew from credit grants.

Monitoring and observability​

  • Fixed a run with no output directory showing a lineage message on its Outputs tab.
  • Fixed folders on a run's Outputs tab not expanding. The pipeline outputs list is now always a tree.

Studios​

  • Fixed long Studio names truncating in the Studios list while the name column still had room.

General​

  • Fixed form controls not repainting after a silent value update.
  • Fixed the Fusion throughput quota never applying at launch.

Seqera Cloud v27.1.0_cycle76

Breaking changes​

A Fusion version selected in the launch form or saved on a pipeline no longer takes effect on its own. Runs use the Fusion version from the Nextflow launcher container unless the Fusion version override is enabled on the compute environment.

Feature updates and improvements​

Co-Scientist​

  • Moved the current page out of the status bar and onto a Context chip in the composer, where it stays visible after a page screenshot is skipped or dismissed.
  • Added arrow-key navigation into and out of a category in the @ mention menu.
  • Changed Esc at the top level of the @ mention menu to close the panel instead of reopening it.

Agents​

  • Added the bound GitHub App credential to an agent's Details tab.
  • Added a message to the Service account picker on the agent form when the workspace has no service account.

Actions​

  • Added a link from an action's Target card to the agent it runs.
  • Added a message to the Agent picker on the action form when the workspace has no agent.

Bug fixes​

Compute environments​

  • Fixed cancelling a run on Google Batch failing and leaving its task jobs running.
  • Fixed runs on EC2 instance types without live console output being marked unknown and dropped from monitoring.

Pipelines​

  • Fixed resuming a run disabling every compute environment when the environment's work directory ends in a slash.

Seqera Cloud v27.1.0_cycle75

Feature updates and improvements​

Co-Scientist​

  • Replaced the Recent shortcut in the @ mention menu with a Search context field, per-category browsing, paginated results, and status badges.

Compute environments​

  • Added Use private address to Azure Batch Forge compute environments, for pool nodes without public IP addresses.
  • Added the instance ID and failing command to setup script warnings in the run execution log.

Studios​

  • Added a link from a Studio's details page to its compute environment.

Service accounts​

  • Added service accounts: non-human identities that belong to an organization and that an agent can run as. Organization owners add, view, edit, and delete them from the new Service accounts tab under Access control.
  • Added workspace roles for service accounts.
  • Added organization membership rules for service accounts. Each service account counts toward the organization's member limit.
  • Marked service accounts in the admin panel. The users list and the Members of organization and Workspace participants tabs show a service account badge and a distinct avatar, and the organization role column reads Service account.

General​

  • Redesigned the organization, workspace, and user profile settings pages.

Bug fixes​

Co-Scientist - projects​

  • Fixed the project Datasets tab showing unusable dataset actions to Launch users and non-functional buttons in empty projects.
  • Fixed relaunching a run from a project's Runs tab returning to the workspace instead of the project.

Pipelines​

  • Fixed Launch users being unable to resume runs of pipelines with Pull latest enabled.
  • Fixed Azure data repositories selected as a run output directory producing an invalid path.
  • Fixed a Fusion version selected in the launch form ignoring the compute environment's Fusion snapshots setting. A selected version with no Fusion snapshots build now fails the launch with an error.

Compute environments​

  • Fixed AWS compute environments reporting an unexpected error instead of an access denial when credentials cannot reach the work directory bucket.

Credentials​

  • Fixed Bitbucket Server credentials with an access token and no password being rejected when adding a pipeline or opening its launch form.

Data Explorer​

  • Fixed the IGV preview losing its reference annotation track, chromosome ideogram, and gene name search.

Data lineage​

  • Fixed selecting a task in global search results opening the run's Tasks tab instead of the task.

Secrets​

  • Fixed pipeline secrets with underscores in their names being wrongly rejected as duplicates.

General​

  • Fixed muted text using the light theme color in the dark theme.
  • Fixed muted and raised surfaces being indistinguishable in the dark theme.
  • Fixed pipeline and compute environment addresses in the public 12.0.0.0/8 and 172.32.0.0-172.37.255.255 ranges being rejected as private.
  • Fixed screen readers not announcing a field's label together with its value.

Seqera Cloud v26.2.0_cycle74

Feature updates and improvements​

Co-Scientist​

  • Made Projects available in organization workspaces to roles with the Projects permission, which existing custom roles don't include.
  • Added the Project workspace role, for a user who launches a project's pipelines, adds datasets, and reads run reports from the Projects view, without the workspace's Launchpad, Runs, Datasets, Compute, or Settings pages.
  • Added a Projects permission category to custom roles.
  • Surfaced proj_ labels as projects in Labels settings.
  • Limited the launch picker on a project's Runs tab to pipelines that carry the project's label.

Pipelines​

  • Added a Fusion version selector to the launch form, and limited both version lists to compatible versions.

Studios​

  • Added Conda packages for custom container images under More settings.
  • Shortened the browser tab title on the Studio details and connect pages to Studio: <name>.

Data Explorer​

  • Added the bucket versioning state (Enabled, Suspended, Disabled, or Unknown) to the About data repository dialog for Amazon S3 and Google Cloud Storage data repositories.

Data lineage​

  • Changed See in Data Explorer on the run Outputs tab to use the output directory from the run's lineage record.

Credentials​

  • Added the Set up Workload Identity Federation in GCP panel to Google Workload Identity credentials created from the compute environment form.

Monitoring​

  • Added a Quick launch action to the empty runs list.

Bug fixes​

Pipelines​

  • Fixed the Add and Update buttons on the action and pipeline forms staying disabled after a pipeline revision failed to load.

Actions​

  • Fixed a paused action that names a deleted pipeline being resumable instead of asking you to point it at a live pipeline.

Compute environments​

  • Fixed Azure Batch Forge compute environment creation accepting a malformed container registry credential ID, or more than one.

Access control​

  • Fixed selecting a template for a custom role not applying its permissions.

General​

  • Fixed the Runs and All runs pages showing no results when opened or reloaded with a search filter in the URL.
  • Fixed cancelled runs showing an empty Metrics tab.

Seqera Cloud v26.2.0_cycle73

Feature updates and improvements​

Monitoring​

  • Added a live task execution timeline to the run Tasks tab, showing each task's queued and running time.

Pipelines​

  • Extended the Nextflow version list back to 23.03, from a previous floor of 25.10.
  • Added the pipeline diagram declared in manifest.diagram to the launchpad pipeline details page.

Studios​

  • Added custom Studio icons, shown in the Studios list and on the Studios page.

Co-Scientist​

  • Moved the sandbox chip into the chat composer toolbar, beside the context chips.

Data lineage​

  • Made data lineage available in organization workspaces for runs on AWS compute environments.
  • Added pipeline:<name> and pipelineId:<id> qualifiers to lineage search, matching a pipeline's runs, tasks, and published files.
  • Added pipeline names to lineage search results and a See syntax tips link to the search modal.
  • Changed data lineage ingestion from SQS polling to SNS notifications and added s3:ListBucket to the lineage IAM policy; manually configured workspaces must be reconfigured.

General​

  • Added the reason an action stopped or failed to the Actions list.
  • Redesigned the Actions list as a table showing each action's source, status, last event, and creator, with usage details in a dialog.
  • Added guided empty states to list pages, naming the next step to take.

Bug fixes​

Co-Scientist​

  • Fixed a closed Co-Scientist chat reopening on page refresh.
  • Fixed the left navigation staying collapsed after closing the Co-Scientist chat.

Pipelines​

  • Fixed GitHub Redeliver not retrying an action trigger whose launch failed.

Studios​

  • Fixed Studios SSH authorization rate limiting applying across all sessions instead of per session.

General​

  • Fixed labels beyond the first 100 missing from the launch form and label search, and label assignments dropping selections not on the current page.
  • Fixed an unstable sort order that repeated or omitted labels when paging through the label list.

Seqera Cloud v26.2.0_cycle72

Breaking changes​

  • Google Batch and Google Cloud compute environments now require a VPC network when Use private address is enabled, and Google Batch also requires a subnet. Both the compute environment form and the API reject a create or update request that enables private addressing without them. Previously, the environment was accepted and failed later at pipeline launch.

Feature updates and improvements​

Compute environments​

  • Added the AWS r9gd instance family to the local NVMe list.
  • Removed the Preview badge from Seqera Compute in the compute environment platform list.

Credentials​

  • Removed the Beta notice from Azure Entra service principal credentials.
  • Added a Set up Workload Identity Federation in GCP panel to Google Workload Identity credentials, listing the values to copy into your Google Cloud project: the OpenID Connect issuer URL, the google.subject mapping that makes Cloud Audit Logs trace activity back to the acting Seqera user, and a recommended attribute condition that pins the workload identity pool to your organization and workspace. The provider, service account email, and token audience fields moved to a Connect the federated identity panel.

Pipelines​

  • Added deduplication of repeated GitHub webhook deliveries to an action, preventing a resend from launching the pipeline a second time. A delivery that cannot be recorded now returns 500, and GitHub offers the resend rather than reporting success.
  • Added an audit log record for every action firing.
  • Added a Created by column to the Actions list.
  • Grouped the action form into Details, Trigger, and Target sections. The form omits the Trigger section for GitHub and Seqera sources, which a webhook endpoint drives instead.

Bug fixes​

Compute environments​

  • Fixed Kubernetes, EKS, and GKE compute environment validation reporting every connection failure as Unexpected error while processing request, so connection timeouts, refused connections, DNS failures, TLS and certificate errors, and endpoints that are not a Kubernetes API server now each report what failed.
  • Fixed GKE cluster discovery reporting a generic 400 for revoked keys, exceeded quotas, and unreachable API endpoints instead of the underlying Google Cloud error.
  • Fixed compute environment validation reusing a cached client from a different compute environment, so correcting a field and resubmitting, or updating credentials, now validates against the new values.
  • Fixed GKE compute environments that use Workload Identity Federation failing with a 500 when reading run logs or downloading files.
  • Fixed Azure Cloud compute environment creation failing with an unexplained error when the credentials cannot read back a resource the forge has just created, so the error now names the resource and the missing read permission.
  • Fixed pipeline additions against Tower Agent compute environments intermittently failing with Timeout waiting for command response.

Studios​

  • Fixed Studios with mounted data links failing to start on Seqera Compute and on AWS Cloud, Azure Cloud, and Google Cloud compute environments.

Seqera Cloud v26.2.0_cycle71

Feature updates and improvements​

Secrets​

  • Migrated the workspace and user secrets lists to the shared row-card table already used by compute environments and credentials. Edit and Delete moved into the row's kebab menu, and the whole row opens the edit form for users with update permission.

Bug fixes​

Credentials​

  • Fixed the inline credentials form in compute environment creation offering fewer options than the Credentials page. AWS supports role-based credentials with external ID generation, Google supports Workload Identity Federation, and Azure uses the same credential fields as that page.
  • Fixed the row actions column reserving an empty strip in the compute environment and credentials lists for users without permission to act on the row.
  • Fixed the credentials kebab menu opening an empty panel for users without permission to act on the row.

Pipelines​

  • Fixed lineage resolution for resumed runs. Each run in a resume chain now shows its own Lineage ID, instead of every run in the chain showing the most recently indexed one. A resumed run shows - while it executes, then its own Lineage ID once it completes.