Skip to content
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

v2 Component I/O page needs to link to Artifacts Reference #3438

Closed
bbrewington opened this issue Jan 26, 2023 · 4 comments
Closed

v2 Component I/O page needs to link to Artifacts Reference #3438

bbrewington opened this issue Jan 26, 2023 · 4 comments

Comments

@bbrewington
Copy link

As a data scientist somewhat new to Kubeflow / GCP Vertex, I’m not necessarily familiar with the v1 SDK. Reading v2 SDK docs on Component I/O, I’m expecting if it uses a term, to have a reference page within the v2 SDK docs (without having to read the actual source code to figure it out)

Basically, “what are all the artifacts and what do they do?”

For a great example, check out how on this dbt reference page, they identify the artifacts “run results” & “manifest”, and link to a reference page for each, fully explaining it: https://docs.getdbt.com/reference/commands/build

screenshot below is from: https://www.kubeflow.org/docs/components/pipelines/v1/sdk-v2/v2-component-io/

New Note

@bbrewington
Copy link
Author

Not sure if this is a separate issue, assuming no

The page: https://www.kubeflow.org/docs/components/pipelines/v1/sdk-v2/component-development/

when it references “Artifact”, links to this page: https://github.com/kubeflow/pipelines/blob/sdk/release-1.8/sdk/python/kfp/dsl/io_types.py

which has a warning saying it’s not relevant for v2. Definitely confused at this knowledge graph. More like a confusion matrix eyyy

New Note

@varodrig
Copy link
Contributor

@bbrewington The link and content no longer exist. Closing this issue. Let us know if you need anything else.

@varodrig
Copy link
Contributor

/close

Copy link

@varodrig: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants