Chris D. Johnson
Chris D. Johnson
Here's a one-liner: `cat catalog.json | jq -sr '.[] | @sh "cat >\(.schema)-\(.name).json
In general: Because this data now exists in many places and has different consumers, it's very hard to know what the source of truth is by each consumer. Because it's...
Is the result of this consistent with how `opm serve` currently merges the stream? The result should be identical assuming there is no advanced/intelligent merge policy.
@joelanford > `opm serve` doesn't merge anything. It loads it all and then errors out (via an internal `opm validate` call) if it finds any duplicates. It appears to do...
Related Enhancement PR: https://github.com/operator-framework/enhancements/pull/116
An alternative that Keycloak could implement: Add separate channels per major version. Their git repo for this is [here](https://github.com/keycloak/keycloak-operator/issues). They could have: ``` alpha-v15 alpha-v16 alpha-v17 alpha ``` This gives...
Per the OLM Dev call today (Aug 15, 2023), we discussed how this "could" be fixed by adding a Subscription config per https://github.com/operator-framework/operator-lifecycle-manager/issues/2923#issuecomment-1480191733. If a PR were created to address,...
> Curious, what use case does this address? Our larger customers want to create large deployment topologies within a single cluster that allow different isolation layers to allow different instances...
@dmesser This is in the scope of the current OLM APIs and it's current capabilities. This is showing what the Deployment Environment/Topology that the Operators will be installed into. Although...