-
Notifications
You must be signed in to change notification settings - Fork 244
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
[PIE-1819] Documentation for Analytics REST API Suites#update and Suite#destroy #2251
[PIE-1819] Documentation for Analytics REST API Suites#update and Suite#destroy #2251
Conversation
Preview URL: https://2251--bk-docs-preview.netlify.app |
5541e0d
to
db1ec94
Compare
https://api.buildkite.com/v2/analytics/organizations/{org.slug}/suites{suite.slug} \ | ||
``` | ||
|
||
Required scope: `write_clusters` |
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.
Required scope: `write_clusters` | |
Required scope: `write_suites` |
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.
whoops I copied it from pipelines docs and forgot to update the scope name. Good catch!
## Update a suite | ||
|
||
```bash | ||
curl -X PUT \ |
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.
[nit]
curl -X PUT \ | |
curl -X PATCH \ |
I believe this is generally better practice and is consistent with pipelines: https://buildkite.com/docs/apis/rest-api/pipelines#update-a-pipeline
|
||
<table class="responsive-table"> | ||
<tbody> | ||
<tr><th><code>name</code></th><td>Name of the new suite.<br><em>Example:</em> <code>"Jasmine"</code>.</td></tr> |
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.
<tr><th><code>name</code></th><td>Name of the new suite.<br><em>Example:</em> <code>"Jasmine"</code>.</td></tr> | |
<tr><th><code>name</code></th><td>Name of the suite.<br><em>Example:</em> <code>"Jasmine"</code>.</td></tr> |
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.
One minor style tweak, otherwise, looks good to me with @swebb's suggestions. 😊
|
||
```bash | ||
curl -X DELETE \ | ||
https://api.buildkite.com/v2/analytics/organizations/{org.slug}/suites{suite.slug} \ |
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.
Style: I don't believe this is necessary.
https://api.buildkite.com/v2/analytics/organizations/{org.slug}/suites{suite.slug} \ | |
https://api.buildkite.com/v2/analytics/organizations/{org.slug}/suites{suite.slug} |
db1ec94
to
a4d65a9
Compare
Add documentation about test analytics Suites#update and Suite#destroy API endpoints
Suites#update:
Suite#destroy: