Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-2890

Add timeline for removal of deprecated resourceCustomizations

    XMLWordPrintable

Details

    • 3
    • False
    • None
    • False
    • Hide
      In {gitops-title} 1.7.0, the `.spec.resourceCustomizations` parameter was deprecated. The deprecated `.spec.resourceCustomizations` parameter is planned to be removed in the upcoming {gitops-title} GA v1.10.0 release. You can use the new formats `spec.ResourceHealthChecks`, `spec.ResourceIgnoreDifferences`, and `spec.ResourceActions` instead.
      Show
      In {gitops-title} 1.7.0, the `.spec.resourceCustomizations` parameter was deprecated. The deprecated `.spec.resourceCustomizations` parameter is planned to be removed in the upcoming {gitops-title} GA v1.10.0 release. You can use the new formats `spec.ResourceHealthChecks`, `spec.ResourceIgnoreDifferences`, and `spec.ResourceActions` instead.
    • Deprecated Functionality
    • GITOPS Sprint 237, GITOPS Sprint 238

    Description

      Story (Required)

      Inform users about removal of deprecated resourceCustomizations in gitops-operator v1.10.0

      Background (Required)

      We have deprecated resourceCustomizations in v1.7.0(gitops v1.7.0 release notes) however we didn't inform users when it will be removed. 

      Approach (Required)

      update our current resourceCustomizations deprecation event & doc notice to specify removal in v1.10

      Acceptance Criteria (Mandatory)

      • resourceCustomizations deprecation event should contain removal timeline
      • resourceCustomizations docs should be updated  

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

      Attachments

        Activity

          People

            rh-ee-sghadi Siddhesh Ghadi
            rh-ee-sghadi Siddhesh Ghadi
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: