fix(deps): update module github.com/openshift-online/ocm-sdk-go to v0.1.492

[red-hat-konflux]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/openshift-online/ocm-sdk-go	v0.1.486 -> v0.1.492

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Release Notes

openshift-online/ocm-sdk-go (github.com/openshift-online/ocm-sdk-go)

v0.1.492: Release 0.1.492

Compare Source

• Update model to 0.0.447
  • Make Topology attribute of ARO-HCP ProvisionShard required and restrict
    its allowed value to shared
  • Expand EtcdEncryption attribute description for ROSA-HCP Clusters

v0.1.491: Release 0.1.491

Compare Source

• Update model to 0.0.446
  • Add AzureShard and ProvisionShardMaestroConfig to ARO-HCP ProvisionShard
    type
  • Remove HypershiftConfig, ManagementCluster, HiveConfig,
    AWSAccountOperatorConfig, GCPProjectOperator, AWSBaseDomain, AWSBaseDomain
    from ARO-HCP ProvisionShard type

v0.1.490: Release 0.1.490

Compare Source

• Update model to 0.0.444
  • Add ExcludedNamespaceSelectors to ingress type

v0.1.489: Release 0.1.489

Compare Source

• Update model to 0.0.443
  • Add Channel field to Cluster type for Y-stream update channel management

v0.1.488: Release 0.1.488

Compare Source

• Update model to 0.0.442
  • Add DeletedClusters new resource to list deleted clusters and get a deleted cluster by its id

v0.1.487: Release 0.1.487

Compare Source

• Add cloud_provider field to CS dns_domains type

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[red-hat-konflux]

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 2 additional dependencies were updated

Details:

Package	Change
github.com/openshift-online/ocm-api-model/clientapi	v0.0.440 -> v0.0.447
github.com/openshift-online/ocm-api-model/model	v0.0.440 -> v0.0.447

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: red-hat-konflux[bot]
Once this PR has been reviewed and has the lgtm label, please assign rcampos2029 for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci]

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a openshift-online member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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-sigs/prow repository.