[WIP] OSDOCS-2210: OSDK-1713 Custom Scorecard storage feature

[michaelryanpeter]

Release: 4.10

OSDOCS-2210

Docs preview: https://deploy-preview-36751--osdocs.netlify.app/openshift-enterprise/latest/operators/operator_sdk/osdk-scorecard#osdk-scorecard-store-output_osdk-scorecard

[netlify]

✔️ Deploy Preview for osdocs ready!

🔨 Explore the source changes: 579536f

🔍 Inspect the deploy log: https://app.netlify.com/sites/osdocs/deploys/62250ca8bcd7620007cc681c

😎 Browse the preview: https://deploy-preview-36751--osdocs.netlify.app

[theishshah]

/lgtm

[jmrodri]

/lgtm

[jmrodri]

/lgtm

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[michaelryanpeter]

/remove-lifecycle stale

[kalexand-rh]

I have some suggestions and style/formatting requests.

[kalexand-rh]

Suggested change

	<.> Set the directory where you want to store your test results, such as `test-results`.
	<.> Set the location of the directory to store your test results, such as `test-results`.

Does this directory have to exist?

[kalexand-rh]

Honestly, I'd rewrite this whole thing without the broken flag and be like "this command store the test results in the test-output directory of your working directory." When the bug is fixed, update the docs to describe the flag.

[sferich888]

+1 The way this is written makes this read as if 'we have this cool new feature, but none of it works - good luck'.

I wouldn't document this till the bug was/is fixed; only document the way's in which it properly works.

[bobfuru]

In preparation for OCP 4.10 GA, I'm moving the Milestone to "Next Release" as this PR did not make the merge by the 4.10 GA date. Post-GA, any open 4.10 PRs fall under the "Next Release" bucket in the same way that 4.6-4.9 PRs are already there. This change does not have any impact on the work in this PR; it's a housekeeping task to keep account of all PRs that had already merged by the 4.10 GA date. 😁

[bergerhoffer]

The branch/enterprise-4.11 label has been added to this PR.

This is because your PR targets the main branch and is labeled for enterprise-4.10. And any PR going into main must also target the latest version branch (enterprise-4.11).

If the update in your PR does NOT apply to version 4.11 onward, please retarget this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[bergerhoffer]

The enterprise-4.12 label has been added to this PR.

This is because your PR targets the main branch and is labeled for enterprise-4.11. And any PR going into main must also target the latest version branch (enterprise-4.12).

If the update in your PR does NOT apply to version 4.12 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.