In Knime hub, could we make it so that config changes get rolled into new versions?
In our case, we are on 1.16.2 and don’t want to update to the next release (major, minor, patch) until we have done testing, but that doesn’t preclude us making maintenance changes to the config (e.g license, certs, etc.), but then the next release will does not include changes when it’s a new version and the diff view is not to helpful for us to know what to manually carry over to the next release.
Hi @mkupfer , thank you for your feedback on this.
We are aware of this issue - if the next Business Hub update (sequence) is downloaded by KOTS on the KOTS Admin Console prior to any config change, the downloaded sequence will not get refreshed to include the later performed config changes.
We have noted this to Replicated, the provider of KOTS as a feature to be improved.
However, unfortunately we have no insight into (or impact on) their roadmaps and cannot provide any details on when this would be improved on their side.