I'm curious, how do you guys manage renovate/keepi...
# atmos
z
I'm curious, how do you guys manage renovate/keeping your vendor.yaml's up-to-date?
Trying to think if I want to keep multiple vendor.yamls, a main one a stable one, a deprecated one, and a latest one vendor.yaml, imports the other 3 renovate keeps "latest" up-to-date. As things are rolled out by our day2 team, versions get gradually moved from latest, to stable, then finally deprecated, and eventually removed after everything is moved off of them aswell as any imported abstracts
e
But we're building native support for this into atmos
👀 1
z
Close ETA?
e
z
We live in self-hosted gitlab if that makes any difference
e
This will make it easier for. you
We are moving all github action functionality natively into atmos, which will make using gitlab easier
❤️ 1
plus open the potential for more native gitlab integrations
I can't comment on timeline; we have a lot of PRs in flight
but if you see atmos.tools/changelog you'll see a pretty good velocity
z
understood. I think for now we just need some processes in place to reduce our blast radius
e
Tests are passing on the source provisioner which I think is the other thing you were interested in
🙌 1
But need to increase test coverage before releasing