Add basic template that uses ImageSpec #43
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
neverett
commented
Dec 8, 2023
neverett
commented
Dec 8, 2023
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
9 tasks
neverett
commented
Dec 11, 2023
neverett
commented
Dec 11, 2023
neverett
commented
Dec 11, 2023
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
3 tasks
Signed-off-by: nikki everett <[email protected]>
|
The integration test issue doesn't look like it's related to this PR I'm okay with merging this and tackling that issue in a separate PR |
Signed-off-by: nikki everett <[email protected]>
…ary requirements, small edits to example python script Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
eapolinario
reviewed
Jan 2, 2024
basic-template-imagespec/{{cookiecuter.project_name}}/workflows/example.py
Outdated
Show resolved
Hide resolved
basic-template-imagespec/{{cookiecuter.project_name}}/workflows/example.py
Show resolved
Hide resolved
basic-template-imagespec/{{cookiecuter.project_name}}/workflows/example.py
Show resolved
Hide resolved
templates.json
Outdated
| {"template_name": "wine-classification", "workflow_name": "training_workflow"} | ||
| {"template_name": "wine-classification", "workflow_name": "training_workflow"}, | ||
| {"template_name": "basic-template-imagespec", "workflow_name": "wf"}, | ||
| {"template_name": "hello_world", "workflow_name": "hello_world_wf"} |
There was a problem hiding this comment.
not sure why we're adding the hello-world example, but the template name is not matching (hello_world instead of hello-world).
There was a problem hiding this comment.
I added ahello-world example in response to this feedback on the new onboarding docs, and went into a bit more detail on my changes here. I'll update the template name, thanks for flagging!
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
|
Congrats on merging your first pull request! 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a basic template that uses ImageSpec, based on the simple example template in #40.
Context
We need a template that uses ImageSpec for the updated onboarding docs (specifically, the new "Creating a Flyte project" and "Flyte project components" pages.) Per the discussion in today's OSS retro planning meeting, it sounds like a long-term plan we may want to consider (with input from appropriate stakeholders) may be to move the content-specific examples we want to keep (bayesian-optimization, mnist-training) from this repo to flytesnacks, remove the wine-classification example, and make the templates in this repo focused on project patterns instead (single cluster deployment, multi-cluster deployment, Dockerfile for those who need to use that instead of ImageSpec).
TODO after merging this PR
pyflyte initing a new project directorybasic-example-dockerfile