Bug 1862500: Use initialization-resource annotation for yaml

[zherman0]

If the initialization-resource annotation value is set for a CR, use it on the yaml pages instead of the alm-example annotation.

Note to self: For testing, use TW's operators that have CR values set in the initialization-resource annotation and then do a patch to change the values from the alm-example: oc patch csv portworx-operator.v1.3.1 --patch "$(cat ~/openshift/portworx-test.json)" --type=merge
and portworx-test.json looks like:

{
  "metadata": {
    "annotations": {
      "operatorframework.io/initialization-resource": "{\n    \"apiVersion\": \"core.libopenstorage.org/v1alpha1\",\n    \"kind\": \"StorageCluster\",\n    \"metadata\": {\n      \"name\": \"portworx-initvalue\",\n      \"namespace\": \"test-operator\"\n    },\n    \"spec\": {\n      \"userInterface\": {\n        \"enabled\": true\n      },\n      \"autopilot\": {\n        \"enabled\": false\n      }\n    }\n  }\n"
    }
  }
}

[openshift-ci-robot]

@zherman0: This pull request references Bugzilla bug 1862500, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.6.0) matches configured target release for branch (4.6.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1862500: Use initialization-resource annotation for yaml

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci-robot]

@zherman0: This pull request references Bugzilla bug 1862500, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.6.0) matches configured target release for branch (4.6.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1862500: Use initialization-resource annotation for yaml

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[zherman0]

@spadgett - Reworked my logic and now I handle the combination of almExamples and Initialization-resource examples.

[zherman0]

/retest

[spadgett]

@zherman0 I think it's simpler just to have a query parameter that is passed in the URL saying to use the initialization resource. If it's set, use the initialization resource. Otherwise always use alm-examples like before.

[openshift-ci-robot]

@zherman0: This pull request references Bugzilla bug 1862500, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.6.0) matches configured target release for branch (4.6.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1862500: Use initialization-resource annotation for yaml

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[zherman0]

/retest

[zherman0]

@spadgett - Switched logic to use URL flag. Ready for review.

[zherman0]

@spadgett - Moved the check for the URL flag out of the parse helper function.

[spadgett]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: spadgett, zherman0

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• frontend/packages/knative-plugin/OWNERS [spadgett]
• frontend/packages/operator-lifecycle-manager/OWNERS [spadgett]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@zherman0: All pull requests linked via external trackers have merged:

• openshift/console#6393

Bugzilla bug 1862500 has been moved to the MODIFIED state.

In response to this:

Bug 1862500: Use initialization-resource annotation for yaml

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.