Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-10528

Product CR - improvement about removed fields

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started

      What

      When a product CR is created with an application plan, and some fields are missing, operator assumes default values for missing fields. When a user then updates the missing fields, for example "trial_period" - the values are taken from the CR, however, if user deletes the fields the values aren't reverted back to their default values but instead, remain at the last known configuration. This can be very misleading.

      We need to ensure that in the product CR, if a value is assumed, then set and deleted, the value is updated to the assumed value instead of remaining at the last known config. Alternatively, update the CR/block removal of fields and update the status of the CR.

      I think in case of application plan - any non value should be 0 which is the default value
      For authentication settings, the default value is user_key, so if OIDC is specified within product CR and then removed, it should revert back to user key auth.

      Alternative is to create INFO message in status stating that the values removed remained at last known configuration.

              Unassigned Unassigned
              mstoklus_rhmi Michal Stokluska
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: