#698 [Docs] Separate Flyte Admin Service.proto into multiple files Issue created by kumare3 Motivation: Why do you think this is important? Currently the entire service API specification is one file. It would be much better to split it into multiple files, as this with automatically separate the generated documentation here More than documentation, it is also easier to reason about the service and eventually if required decompose into multiple processes (though this is not a strict requirement) Goal: What should the final outcome look like, ideally? Separate documents for execution_service.proto workflow_service.proto task_service.proto etc Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. 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 flyteorg/flyte

#698 [Docs] Separate Flyte Admin Service.proto into multiple files Issue closed as not planned by github-actions[bot] flyteorg/flyte

#698 [Docs] Separate Flyte Admin Service.proto into multiple files Issue reopened by katrogan flyteorg/flyte