-
Notifications
You must be signed in to change notification settings - Fork 139
Add initial Stacks API documentation #826
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
| `POST` | `/stack-plans/:stack_plan_id/replan` | Call this endpoint to [replan stack plan](#replan-stack-plan).| | ||
| `PATCH` | `/stacks/:stack_id` | Call this endpoint to [update a stack](#update-a-stack).| | ||
|
||
## List stacks |
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.
I wonder if it would be helpful to have a "Requirements" section above this where we can talk about specific permissions/tokens are user requires to interact with this endpoints? We did something similar on the Projects API page, see https://developer.hashicorp.com/terraform/cloud-docs/api-docs/projects#requirements.
|
||
| Parameter | Description | | ||
| -------------------- | ------------------------------------------------------- | | ||
| `:organization_name` | The name of the organization to list the stacks of. | |
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.
Something I've done before is list the query parameters section. We could list the valid include
data and any search/filter/pagination. An example of the policy sets query parameter section: https://developer.hashicorp.com/terraform/cloud-docs/api-docs/policy-sets#query-parameters
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.
Had another look through! One small nitpick and I think we still have to add the query params but otherwise, I think we are ready for the Documentation Team to review!
| `GET` | `/stack-diagnostics/:stack_diagnostic_id` | Call this endpoint to [show stack diagnostic](#show-stack-diagnostic).| | ||
| `GET` | `/stack-configurations/:stack_configuration_id/stack-diagnostics` | Call this endpoint to [list stack configuration diagnostics](#list-stack-configuration-diagnostics).| | ||
| `GET` | `/stacks/:stack_id/stack-plans` | Call this endpoint to [list stack plans](#list-stack-plans).| | ||
| `GET` | `/stack-plans/:stack_plan_id/` | Call this endpoint to [show stack plan](#show-stack-plan).| |
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.
Nitpick:
| `GET` | `/stack-plans/:stack_plan_id/` | Call this endpoint to [show stack plan](#show-stack-plan).| | |
| `GET` | `/stack-plans/:stack_plan_id` | Call this endpoint to [show stack plan](#show-stack-plan).| |
Hi @aaabdelgany! Heads up that we will be migrating the content from So this is a heads up that after the migration happens I'll close this PR and will let you know when you are good to recreate it! Apologies about the extra work you have to do though! |
Hello @aaabdelgany! The UDR migration has occurred, and the HCP Terraform documentation version now lives in the unified documentation repository. I'm going to close this PR since we are no longer serving this content from this repo, but please feel free to recreate your PR in the UDR repository within the HCP Terraform documentation and tag me if you need a review: |
What
This PR adds the basic api documentation for Stacks.
Why
Stacks has hit open beta so it's time we documented the api. This will likely be the first PR among many since the API surface area is pretty expansive but hopefully we can get the most useful/frequently hit endpoints.
Screenshots
Merge Checklist
If items do not apply to your changes, add (N/A) and mark them as complete.
Pull Request
Content
Reviews