(This issue is aimed primarily for BI admins, as it requires access to the deployment stack)
It'd be super cool if every pull request spins up a temporary preview deployment of BI Files. It would be useful to see any UI changes too, on the go.
For example, PR 23 might get pr-23.preview.files.betterinformatics.com, and you can browse a deployed version of the PR filled with test data. When the PR is closed or merged, the deployment would get taken down.
I believe this should be possible by somehow using wildcard Ingress routes in our Kubernetes configuration, and maybe spinning up temporary postgres/bi-files/minio pods based on webhooks or CI. I've only thought about this briefly though.
Argo & Flux CD would probably usually be the best choice for something like this, but they won't work under our deployment environment, since we only have control over one Kubernetes namespace in Tardis (when both Argo & Flux requires multi-namespace + cluster admin permissions).
(This issue is aimed primarily for BI admins, as it requires access to the deployment stack)
It'd be super cool if every pull request spins up a temporary preview deployment of BI Files. It would be useful to see any UI changes too, on the go.
For example, PR 23 might get
pr-23.preview.files.betterinformatics.com, and you can browse a deployed version of the PR filled with test data. When the PR is closed or merged, the deployment would get taken down.I believe this should be possible by somehow using wildcard Ingress routes in our Kubernetes configuration, and maybe spinning up temporary postgres/bi-files/minio pods based on webhooks or CI. I've only thought about this briefly though.
Argo & Flux CD would probably usually be the best choice for something like this, but they won't work under our deployment environment, since we only have control over one Kubernetes namespace in Tardis (when both Argo & Flux requires multi-namespace + cluster admin permissions).