There's a lot of stuff in the repo now that doesn't necessarily need to have the same release cycle as the Armada Go code. This results in unnecessary complexity. Any objections to moving the DotNet client/Python client/Airflow stuff into separate repos?
The thing we need to address to make that work is proto. Possible solutions include:
Add a script to client repos that pulls in the latest proto from the main Armada repo.
When building clients in CI, automatically pull in the latest proto files from the main repo.
Add a separate repo to which we automatically sync proto from the main Armada repo and pull those files in when building clients.
There's a lot of stuff in the repo now that doesn't necessarily need to have the same release cycle as the Armada Go code. This results in unnecessary complexity. Any objections to moving the DotNet client/Python client/Airflow stuff into separate repos?
The thing we need to address to make that work is proto. Possible solutions include:
┆Issue is synchronized with this Jira Task by Unito