-
Notifications
You must be signed in to change notification settings - Fork 581
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
Add Tuple idl #5720
base: master
Are you sure you want to change the base?
Add Tuple idl #5720
Conversation
Signed-off-by: Mecoli1219 <[email protected]>
Signed-off-by: Mecoli1219 <[email protected]>
Signed-off-by: Mecoli1219 <[email protected]>
Signed-off-by: Mecoli1219 <[email protected]>
Signed-off-by: Mecoli1219 <[email protected]>
case *core.LiteralType_TupleType: | ||
// TO_DISCUSS: How to handle the tuple interface in Inputs field of flytectl? | ||
// | ||
// [Example usage] | ||
// inputs: | ||
// tuple_data: | ||
// key1: "foo" | ||
// key2: 123 | ||
|
||
vMap, ok := v.(map[string]interface{}) | ||
if !ok { | ||
return nil, errors.Errorf("Expected a map[string]interface{} for tuple type, got [%v]", v) |
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.
Can you explain more?
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.
In this part, the LiteralType is already given, so the name of the tuple and the order of each field should be already defined. The only thing that is missing is the value of each field.
Therefore, we only need to provide the value of each tuple field (via the key-value pair of each field) in flytectl
for the registered task or workflow for further execution needs.
Tracking issue
#1337
#3158
#4358
Why are the changes needed?
What changes were proposed in this pull request?
How was this patch tested?
Setup process
Screenshots
Check all the applicable boxes
Related PRs
RFC: #5699
Docs link