-
Notifications
You must be signed in to change notification settings - Fork 943
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
Changing old API links #6199
Changing old API links #6199
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
website/blog/2022-05-03-making-dbt-cloud-api-calls-using-dbt-cloud-cli.md
Outdated
Show resolved
Hide resolved
website/docs/docs/cloud/connect-data-platform/about-connections.md
Outdated
Show resolved
Hide resolved
Changing links to proper new links
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.
looks good! left a few suggs for ya
@@ -691,7 +691,7 @@ Archived release notes for dbt Cloud from 2023 | |||
|
|||
**Beginning June 1, 2023,** developers on the dbt Cloud multi-tenant application will be able to self-serve access to their account’s run history through the dbt Cloud user interface (UI) and API for only 365 days, on a rolling basis. Older run history will be available for download by reaching out to Customer Support. We're seeking to minimize the amount of metadata we store while maximizing application performance. | |||
|
|||
Specifically, all `GET` requests to the dbt Cloud [Runs endpoint](https://docs.getdbt.com/dbt-cloud/api-v2-legacy#tag/Runs) will return information on runs, artifacts, logs, and run steps only for the past 365 days. Additionally, the run history displayed in the dbt Cloud UI will only show runs for the past 365 days. | |||
Specifically, all `GET` requests to the dbt Cloud [Runs endpoint](https://docs.getdbt.com/dbt-cloud/api-v2#/) will return information on runs, artifacts, logs, and run steps only for the past 365 days. Additionally, the run history displayed in the dbt Cloud UI will only show runs for the past 365 days. |
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.
the link text and the link URL doesn't seem to match. is there still a Runs
endpoint?
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.
Yes, but there is no landing page for it anymore. It will be on the sidebar. I guess we could just land on the first page in the runs list. I'll change it to that
@@ -936,7 +936,7 @@ Archived release notes for dbt Cloud from 2023 | |||
|
|||
This maximum limit applies to [multi-tenant instances](/docs/cloud/about-cloud/access-regions-ip-addresses) only, and _does not_ apply to single tenant instances. | |||
|
|||
Refer to the [Pagination](https://docs.getdbt.com/dbt-cloud/api-v2-legacy#section/Pagination) section for more information on this change. | |||
Refer to the [Pagination](https://docs.getdbt.com/dbt-cloud/api-v2#/) section for more information on this change. |
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 might be missing something. i don't see a Pagination
section on https://docs.getdbt.com/dbt-cloud/api-v2#/
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.
You have to scroll down to see it on the page we link to. Can't anchor link to it like we could in the old APIs. I know Gideon is working on enhancements
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.
oh i see. i was looking at the sidebar.
as an idea, maybe "... Pagination section on the API v2 page ..." or something?
totally non-blocking.
Co-authored-by: Ly Nguyen <107218380+nghi-ly@users.noreply.github.com>
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.
approving! left one n/b sugg in case it's helpful
What are you changing in this pull request and why?
Changes legacy API links to the newer V2 API.
Removed an old migration page
Checklist