Add Pipelines product 'Service Quotas' page #2774
Conversation
github-actions
bot
added
the
pipelines
|
Preview URL: https://2774--bk-docs-preview.netlify.app |
mitchbne
force-pushed
the
service-quotas
branch
2 times, most recently
from
2b1b7a1
to
016dbc3
Compare
mitchbne
force-pushed
the
service-quotas
branch
from
2a42959
to
cc9963a
Compare
mitchbne
force-pushed
the
service-quotas
branch
from
cc9963a
to
6578eb6
Compare
data/nav.yml
Outdated
| @@ -391,6 +391,8 @@ | |||
| - name: "Cluster queue metrics" | |||
| path: "pipelines/cluster-queue-metrics" | |||
| pill: "beta" | |||
| - name: "Service Quotas" | |||
| path: "pipelines/service-quotas" | |||
There was a problem hiding this comment.
I note you've got this under Pipelines, but a handful of the limits are not pipelines-specific. I wonder if we need a global page? or just limit what's on this one to pipelines ones?
There was a problem hiding this comment.
Perhaps we do need a global page. At the moment, our navigation has:
Are you envisioning a new nav link?
There was a problem hiding this comment.
Probably need guidance from @gilesgas on that, but the content on this page atm doesn't really fit under pipelines
There was a problem hiding this comment.
Where are the docs for setting up organisations, teams, permissions etc?
There was a problem hiding this comment.
The content on this page atm doesn't really fit under pipelines.
Yeah, you're right. It feels like we're missing a concept of a global/cross-product area
Where are the docs for setting up organisations, teams, permissions etc?
At the moment those pages sit under the Pipelines navigation link - https://buildkite.com/docs/team-management/permissions
There was a problem hiding this comment.
Oh yeah, these are also definitely not pipelines haha
pages/pipelines/service_quotas.md
Outdated
| { | ||
| title: "Invitations per organization", | ||
| description: "The maximum number of pending invitations for an organization", | ||
| default_value: "20 invitations" |
There was a problem hiding this comment.
Another general thought – how do we keep these values synced with what's in bk/bk?
There was a problem hiding this comment.
An assertion spec in bk/bk, with a link to this guide doc to update it if an engineer changes the default?
There was a problem hiding this comment.
We might be able to leverage some internal tooling options (e.g. https://github.com/danger/danger) to help us out here in the bk/bk side 👀
|
Hey @dabarrell and @mitchbne , Sorry it's taken me a while to revisit this PR, now that we have the new Platform area for the docs, I'm wondering if we could publish this work somewhere in here instead? If so, I can fix this up for you... |
github-actions
bot
removed
the
pipelines
In this PR we introduce a Service Quotas page for limits within the Pipelines product.