[dagster-fivetran][docs] Migrate Fivetran docs to new doc site #26485
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
Deploy preview for dagster-docs-beta ready! Preview available at https://dagster-docs-beta-7r9bnoto1-elementl.vercel.app Direct link to changed pages: |
maximearmstrong
force-pushed
the
maxime/migrate-fivetran-docs
branch
from
cfa3693 to
e61d3b4
Compare
|
|
||
| ## Represent Fivetran assets in the asset graph | ||
|
|
||
| To load Fivetran assets into the Dagster asset graph, you must first construct a <PyObject module="dagster_fivetran" object="FivetranWorkspace" /> resource, which allows Dagster to communicate with your Fivetran workspace. You'll need to supply your account ID, API key and API secret. See [Getting Started](https://fivetran.com/docs/rest-api/getting-started) in the Fivetran REST API documentation for more information on how to create your API key and API secret. |
There was a problem hiding this comment.
The PyObject components are creating an undefined. Is that specific to Fivetran or more broadly an issue with the new docs? If more broad we can merge and make a follow-up ticket to fix this.
There was a problem hiding this comment.
I get the same PyObject not implemented yet error in the I/O manager guide that is already in the docs
In the I/O manager guide:
In the Fivetran docs:
There was a problem hiding this comment.
cc @neverett
There was a problem hiding this comment.
Yeah, I agree with @cmpadden -- let's merge this, and I'll make a ticket to follow up on PyObject implementation in new docs.
maximearmstrong
force-pushed
the
maxime/migrate-fivetran-docs
branch
from
e61d3b4 to
d82cf47
Compare
Summary & Motivation
Copy and migrate new Fivetran docs to new site, see original PR #26026
Removing
docs-to-migratetag from the original PRHow I Tested These Changes
BK.