[codex] Add workspace governance guidance for enterprise onboarding#1270
Draft
llewellyn-sl wants to merge 2 commits intomasterfrom
Draft
[codex] Add workspace governance guidance for enterprise onboarding#1270llewellyn-sl wants to merge 2 commits intomasterfrom
llewellyn-sl wants to merge 2 commits intomasterfrom
Conversation
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| - Use shared workspaces when you want to centralize reusable pipelines or compute environments for multiple groups, while still letting each consuming workspace keep its own participants and day-to-day operations. | ||
| - Keep workspace credentials aligned to the data and infrastructure that the workspace is expected to operate. Avoid reusing a single broad credential across unrelated groups when separate credentials or narrower scopes are available. | ||
|
|
||
| This model makes it easier to onboard new groups consistently, audit who can access a given bucket or compute environment, and limit the blast radius of later credential changes. |
Member
There was a problem hiding this comment.
Suggested change
| This model makes it easier to onboard new groups consistently, audit who can access a given bucket or compute environment, and limit the blast radius of later credential changes. | |
| This model makes it easier to onboard new groups consistently, audit who can access a given bucket or compute environment, and limit the impact of later credential changes. |
Member
|
Adding comments rather than editing so others can evaluate the PR as well. Largely, this is a good draft. The content appears reasonable for addressing the questions raised in the ticket. My GCP knowledge is limited. Editorially, I think the tense drifts a little in the added text. Also, some very long sentences could be shorter. I'm also not sure if this is the best location for "Workspace planning for larger organizations"; to me, it should be called out before creating a workspace section, as it frames some of the decisions/steps for the rest of the page. |
justinegeffen
added
1. Editor review
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
3 participants
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.
Summary
Source
Doc target
platform-cloud→platform-cloud/docs/orgs-and-teams/workspace-management.mdplatform-cloud→platform-cloud/docs/credentials/data_repositories.mdRationale
The ticket asked for enterprise onboarding guidance without introducing a large new guide. These edits keep the change on existing pages that users already consult when setting up organization workspaces and GCP data access, while adding the missing governance and credential-scoping advice that had been handled ad hoc.
Validation
node_modulesare not available in the automation cloneFollow-up questions / gaps