-
Notifications
You must be signed in to change notification settings - Fork 61
Added template configuration to task template #358
Conversation
Signed-off-by: Daniel Rammer <[email protected]>
Signed-off-by: Daniel Rammer <[email protected]>
Signed-off-by: Daniel Rammer <[email protected]>
Codecov Report
@@ Coverage Diff @@
## master #358 +/- ##
=======================================
Coverage 73.71% 73.71%
=======================================
Files 18 18
Lines 1377 1377
=======================================
Hits 1015 1015
Misses 311 311
Partials 51 51
Flags with carried forward coverage won't be shown. Click here to find out more. Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
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.
Let's add more code comments to explain the behavior. I'm pretty sure we will get a lot of questions here...
Why do we need this, why not use the one of |
@kumare3 e.g. for my usecases it boils down to setting some things like |
Signed-off-by: Daniel Rammer <[email protected]>
Signed-off-by: Daniel Rammer <[email protected]>
* added template to task template Signed-off-by: Daniel Rammer <[email protected]> * updated docs Signed-off-by: Daniel Rammer <[email protected]> * updated pod_template_name location to TaskMetadata proto message Signed-off-by: Daniel Rammer <[email protected]> --------- Signed-off-by: Daniel Rammer <[email protected]>
TL;DR
This PR adds a template field to the
TaskTemplate
which contains either aPodTemplate
name or a marshaledPodTemplate
struct.Type
Are all requirements met?
Complete description
^^^
Tracking Issue
flyteorg/flyte#3123
Follow-up issue
NA