[feature] Re-enable extra_code parameter for Python components.

Feature Area

/area sdk

What feature would you like to see?

In KFP v1, there’s an option to extend lightweight python components via extra_code which enables to have non-primitive values as defaults supported. However in KFPv2 this seems to be largely unsupported. Even in KFP v1, seems to be discouraged to use as create_component_from_func does not support it and func_to_container_op seems to be officially discouraged by maintainers (see: #7794 )

What is the use case or pain point?

Extending python lightweigh decorator functionality to use custom defaults that are not primitives.

Is there a workaround currently?

func_to_container_op in KFP v1 does seem to work fine. However this ask is more related to keep this functionality moving forward.

---

Love this idea? Give it a 👍. We prioritize fulfilling features with the most 👍.

[casassg]

@connor-mccarthy I think this won’t likely work. Essentially what you are asking is users to redo the entire lightweight python decorator just to support non-native types. This seems quite the added overhead for something that seems rather a common use case imho.

[connor-mccarthy]

Thanks, @casassg. That explanation is very helpful and makes a compelling case for including an extra_code parameter.

BTW: Support in lightweight components for custom artifact types from a third-party library is a feature that will be added soon. It doesn’t solve for all of the use cases you’re describing, but would for the Input[MyCustomArtifact] use case.