[BUG] Use remote LP with default inputs and no fixe inputs is not working

[andresgomezfrr]

Describe the bug

Use remote LP with default input and no fixed inputs fails during registration time with:
https://github.com/flyteorg/flytekit/blob/master/flytekit/core/promise.py#L972

    raise _user_exceptions.FlyteAssertion("Missing input `{}` type `{}`".format(k, var.type))

Expected behavior

The LP should be registered properly if the inputs are provided using the default inputs even if there are no fixed inputs configured.

Additional context to reproduce

No response

Screenshots

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[runllm]

To address the bug where using a remote Launch Plan (LP) with default inputs and no fixed inputs fails during registration, it's important to ensure that the default inputs are correctly specified and match the expected types defined in the workflow. The error you encountered suggests a mismatch or absence of required inputs during the LP registration process.

For a scheduled launch plan, either fixed inputs or default inputs with default values must be provided. If a default input is marked as required, the corresponding fixed input should be specified. If it has a default value, a fixed input is not necessary. This behavior should be validated during the LP registration to prevent such errors (source).

Would you like more detailed guidance on how to correctly configure and validate the inputs for your Launch Plan to avoid this issue?

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!

[davidmirror-ops]

Fixed on flyteorg/flytekit#2372