Closed rm3l closed 4 months ago
Since we are moving this repo to rhd/rhdh-operator repo, and there's currently no plan to also contribute this to a backstage/operator repo, this will likely be not required.
Instead we can merge the two CSVs into a single downstream one and simplify the resulting repo.
As part of the migration from janus-idp to redhat-developer in https://issues.redhat.com/browse/RHIDP-1021, this will be tracked in https://issues.redhat.com/browse/RHIDP-2387 and https://issues.redhat.com/browse/RHIDP-2389
/kind user-story
User Story
As an operator developer, I want to have the RHDH bundle manifest generated So that I can simplify the maintenance of this CSV and reduce the potential errors caused by an out-of-sync downstream bundle (especially regarding the operator permissions, as caught for example in #360 and #351).
Kustomize could be a great fit for this, but any better solution is also welcome. Similar to the
make bundle
command which generates the CSV for the upstream operator (which is version-controlled for review), we could imagine amake bundle-rhdh
that would generate the CSV for RHDH off of this upstream CSV using Kustomize overlays/patches. It will still need to be version-controlled for review in.rhdh/bundle
.Acceptance Criteria
make bundle-rhdh
target that would generate the RHDH CSV off of the upstream CSV (frommake bundle
)Links
Context
Do you have an idea what prevents us to auto generate the CSV file for downstream instead?
_Originally posted by @gazarenkov in https://github.com/janus-idp/operator/pull/361#discussion_r1603045859_