Road to first class routes in lagoon api

[Schnitzel]

1. create new lagoon environment variable which expects a json object the same structure as the routes key in the .lagoon.yml which is passed to lagoon-build-deploy pod and then merged with what is found in the .lagoon.yml for the environment. This is a bit risky but the easiest to implement.
2. implement route objects in lagoon api and pass them to lagoon-build-deploy pod which then merges them
3. Have lagoon-build-deploy fill route objects in lagoon api after a deployment and deprecate .lagoon.yml routes setting
4. with new Lagoon Major Vesrion: Only use route objects in lagoon api and no longer deploy .lagoon.yml routes

[lind101]

Hey all,

We would love to see this implimented! Let me know if you need any help testing!

[shreddedbacon]

We've discussed a proof of concept for getting this in by using an environment variable defined in the API that contains the data structure that would be passed to the build process to create them at the next deployment.

The idea will be that we will merge this into the existing .lagoon.yml some how to make sure that the existing process of creating routes through a build remain the same.

I'm working on if this is possible to do, as the .lagoon.yml structure isn't really ideal.