Closed szEvEz closed 7 months ago
removing manifests in deploy/ so we do not need to maintain two sets of config - we could think about automating it
Well, it was automated. :)
removing manifests in deploy/ so we do not need to maintain two sets of config - we could think about automating it
Well, it was automated. :)
But generating the helm chart from the deployment manifests using helmify is currently dropping configuration. How do we want to proceed here?
removing manifests in deploy/ so we do not need to maintain two sets of config - we could think about automating it
Well, it was automated. :)
But generating the helm chart from the deployment manifests using helmify is currently dropping configuration. How do we want to proceed here?
I'd be fine with generating the deploy-files from the helm-charts or modifying helmify so it does not drop the configuration.
NB: not everybody uses (or likes) helm and I want to support that. Removing the static files would also be a breaking change.
Hm, you completely removed the documentation on how to use it without helm. Can you re-add this please?
Hm, you completely removed the documentation on how to use it without helm. Can you re-add this please?
Sure, done!
From my point of view there is also no real benefit of storing the deploy manifests in the repo, if there is manual configuration required (adapting url and secret). If we could get around that, I'd love to generate a "deployment.yaml" and attach it to the release, like cert-manager does it for instance.