-
Notifications
You must be signed in to change notification settings - Fork 690
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
[Docs] Rename container_image to image for improved UX #6211
base: master
Are you sure you want to change the base?
[Docs] Rename container_image to image for improved UX #6211
Conversation
Signed-off-by: JiangJiaWei1103 <waynechuang97@gmail.com>
Code Review Agent Run Status
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #6211 +/- ##
=======================================
Coverage 36.90% 36.90%
=======================================
Files 1317 1317
Lines 134061 134061
=======================================
+ Hits 49474 49479 +5
+ Misses 80294 80289 -5
Partials 4293 4293
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@@ -17,7 +17,7 @@ For example, [flytekitplugins-envd](https://github.com/flyteorg/flytekit/blob/c0 | |||
For every {py:class}`flytekit.PythonFunctionTask` task or a task decorated with the `@task` decorator, | |||
you can specify rules for binding container images. By default, flytekit binds a single container image, i.e., | |||
the [default Docker image](https://ghcr.io/flyteorg/flytekit), to all tasks. To modify this behavior, | |||
use the `container_image` parameter available in the {py:func}`flytekit.task` decorator, and pass an | |||
use the `image` parameter available in the {py:func}`flytekit.task` decorator, and pass an |
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.
Not sure I follow
I still see container_image
as the arg name in the task
API
https://docs.flyte.org/en/latest/api/flytekit/generated/flytekit.task.html
I think there's some discussion around changing it to be image
indeed but not in effect AFAIK
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.
+1 but please don't merge this until there's a deployed change (non-beta) in flytekit.
docs can be merged after the official Flyte release is out so it's okay to be a little delayed.
Thanks!
Tracking issue
NA
Why are the changes needed?
To enhance the user experience, the concept of
container
should be abstracted from flytekit users.What changes were proposed in this pull request?
Rename
container_image
toimage
forflytekit.task()
decorator.Check all the applicable boxes
Related PRs
flyteorg/flytekit#3094
Docs link