Uploaded image for project: 'Hybrid Application Console'
  1. Hybrid Application Console
  2. HAC-1616

Support model flag extension in HAC Core

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • Core
    • None
    • False
    • False
    • None

      We already support the model flag extension point in the dynamic plugin SDK (see https://github.com/openshift/dynamic-plugin-sdk/blob/main/packages/lib-core/src/extensions/feature-flags.ts#L14) Now we must populate the model feature flags in HAC Core via API discovery for HAC Dev and HAC BS.

      See slack threads:
      https://coreos.slack.com/archives/C02EQERSV3N/p1655831932631929

      https://coreos.slack.com/archives/C02EQERSV3N/p1655387844714439?thread_ts=1655362979.611449&cid=C02EQERSV3N

      Acceptance Criteria:

      • HAC Core will utilize the model feature flag extension exposed by the core SDK here: https://github.com/openshift/dynamic-plugin-sdk/blob/main/packages/lib-core/src/extensions/feature-flags.ts#L14
      • Using API discovery, when a CRD is detected on the cluster, a model feature flag extension will be populated for that CRD. For example, if the hac-bs integration controller CRD is present on the cluster, hac-core should flip the model feature flag for that CRD to indicate its presence. This is the same behavior as in OCP console.
      • HAC plugins can then consume these flags to determine if they should enable/disable themselves

            khala-1 Karel Hala
            bflorkie@redhat.com Bryan Florkiewicz
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: