Open dan1el-k opened 6 months ago
Hi @dan1el-k. I think #201 may have addressed this by, among other things, allowing users to pass whatever flags they want to the Argo CD repo server (which is actually invoked more as a library here).
Although merged, this just has not been released yet because it's a large breaking change that is not yet documented.
Hi @dan1el-k. I think #201 may have addressed this by, among other things, allowing users to pass whatever flags they want to the Argo CD repo server (which is actually invoked more as a library here).
Although merged, this just has not been released yet because it's a large breaking change that is not yet documented.
Ahh, now it makes sense. In our tests we were wondering that the CRDs are not really matching the docs as well as the argocd-schema.json + schema.json.
Looking forward to test the new release then :). Thanks !!
@dan1el-k I just cut v0.1.0-rc.34
, but it's not integrated into "Kargo proper" yet.
@dan1el-k I just cut
v0.1.0-rc.34
, but it's not integrated into "Kargo proper" yet.
@krancour, just saw two weeks ago kargo 0.3.2 were release. And also begin of January v0.1.0-rc.34 were merged to main. https://github.com/akuity/kargo/commit/de1afba0f4d199c34da44aedaddb042596ebcb6d When do you plan including it into the release ?
Issue
Currently kargo-render uses a flag
--load-restrictor LoadRestrictionsRootOnly
in case of kustomize, which actually blocks the usage ofkustomize remote bases
orkustomize remote components
.Error
Proposal
kustomize remote base
orremote components
by using kustomize flag--load-restrictor LoadRestrictionsNone
git submodules
as an equivalent way to render manifests into another repo.