#506 [Feature] Set launch plan active should accept a named entity rather than identifier Issue created by katrogan Motivation: Why do you think this is important? As of now, the only field that can change in a LaunchPlanUpdateRequest is the launch plan state. At most one launch plan named entity, that is launch plans sharing a project, domain and name can ever be made active. Therefore, deactivating a launch plan is to set all launch plans for a named entity inactive. Goal: What should the final outcome look like, ideally? It should be possible to disable a launch plan without specifying the version. In the same vein, it could make sense to specify the latest launch plan version by also updating a launch plan by named entity identifier without a version. Describe alternatives you've considered The current approach where a full identifier is required. Flyte component ☐ Overall ☐ Flyte Setup and Installation scripts ☐ Flyte Documentation ☐ Flyte communication (slack/email etc) ☐ FlytePropeller ☑︎ FlyteIDL (Flyte specification language) ☑︎ Flytekit (Python SDK) ☑︎ FlyteAdmin (Control Plane service) ☐ FlytePlugins ☐ DataCatalog ☐ FlyteStdlib (common libraries) ☐ FlyteConsole (UI) ☐ Other [Optional] Propose: Link/Inline If you have ideas about the implementation please propose the change. If inline keep it short, if larger then you link to an external document. Additional context Add any other context or screenshots about the feature request here. Is this a blocker for you to adopt Flyte Please let us know if this makes it impossible to adopt Flyte flyteorg/flyte