SPLAT-2603: Updated AWS dedicated host id validation pattern

[vr4manta]

SPLAT-2603

Changes

• Modified the AWS dedicated host validation pattern to include older deprecated host id pattern of 8 alphanumeric

Notes

CodeRabbit in a separate PR had found that AWS has two patterns for this. It seems this pattern for 8 alphanumeric is an older deprecated ID format that was changed in 2018. We are updating our logic just in case some customer still owns one of these older instances and wants to try to use it with OCP.

[openshift-ci-robot]

@vr4manta: This pull request references SPLAT-2603 which is a valid jira issue.

Details

In response to this:

SPLAT-2603

Changes

• Modified the AWS dedicated host validation pattern to include older deprecated host id pattern of 8 alphanumeric

Notes

CodeRabbit in a separate PR had found that AWS has two patterns for this. It seems this pattern for 8 alphanumeric is an older deprecated ID format that was changed in 2018. We are updating our logic just in case some customer still owns one of these older instances and wants to try to use it with OCP.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@vr4manta: This pull request references SPLAT-2603 which is a valid jira issue.

Details

In response to this:

SPLAT-2603

Changes

• Modified the AWS dedicated host validation pattern to include older deprecated host id pattern of 8 alphanumeric

Notes

CodeRabbit in a separate PR had found that AWS has two patterns for this. It seems this pattern for 8 alphanumeric is an older deprecated ID format that was changed in 2018. We are updating our logic just in case some customer still owns one of these older instances and wants to try to use it with OCP.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@vr4manta: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[vr4manta]

/assign @damdo

[damdo]

Nice!

TY

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: damdo

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [damdo]

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

[vr4manta]

/verified by @vr4manta via manual and unit tests
This is being added to our tests as well.

[openshift-ci-robot]

@vr4manta: This PR has been marked as verified by @vr4manta via manual and unit tests.

Details

In response to this:

/verified by @vr4manta via manual and unit tests
This is being added to our tests as well.

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 openshift-eng/jira-lifecycle-plugin repository.