Skip to content

MCO-2411: Add AWS marketplace AMI band check target - #6365

Open
djoshy wants to merge 2 commits into
openshift:mainfrom
djoshy:add-aws-marketplace-periodic-target
Open

MCO-2411: Add AWS marketplace AMI band check target#6365
djoshy wants to merge 2 commits into
openshift:mainfrom
djoshy:add-aws-marketplace-periodic-target

Conversation

@djoshy

@djoshy djoshy commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

- What I did

Marketplace-published RHCOS boot images can drift from what MCO supports without any alerting today. This tool will help in alerting the MCO team when the drift is larger than expected. This is to be run manually by an engineer or an AI agent and not designed to be run as a Prow periodic.

This PR does the following:

  • Extracts pkg/controller/bootimage/marketplace fromaws_helpers.go (shared by the controller and the tool).
  • Adds devex/cmd/check-aws-marketplace-skew (make check-aws-marketplace-skew), checks published Marketplace AMIs per product code against MCO's boot-image skew band, fetching both bounds live from GitHub (no local checkout needed).

- How to verify it
AWS marketplace tests should continue to pass, the refactor should have no effect on the functionality of this feature.

When the new target is run locally(assuming AWS and GitHub tokens have been set up), the output should look like so:

$ make check-aws-marketplace-skew
WHAT_PATH=devex/cmd/check-aws-marketplace-skew WHAT=check-aws-marketplace-skew GOTAGS="" hack/build-go.sh
Using version from git...
Building github.com/openshift/machine-config-operator/devex/cmd/check-aws-marketplace-skew (93c54c90, 93c54c909097ff2451e5bdf38c2cfc5fc2977355) for linux/amd64
Skew-limit floor: RHCOS 9.2 (OCP 4.13.0)
Installer ceiling (arm64): 10.2
Installer ceiling (x86_64): 10.2

PRODUCT          PRODUCT ID                            RESULT  MATCHED AMI            DETAIL
OCP x86_64       59ead7de-2540-4653-a8b0-fa7926d5c845  PASS    ami-0b9620e51a0f7930b  9.6.20260210-0
OKE x86_64       963b36c3-de6f-48ed-b802-2b38b2a2cdeb  PASS    ami-0d73ab1083b42d01d  9.6.20260210-0
OPP x86_64       f5da01a6-d046-487c-9072-42fe53b1cad4  PASS    ami-0cffc6b4f37f87305  9.6.20260210-0
OCP EMEA x86_64  962791c7-3ae5-46d1-ba62-c7a5ebac54fd  PASS    ami-09d9a5aa0051b53ce  9.6.20260210-0
OKE EMEA x86_64  7026c8d7-392c-4010-b93c-f93f7bc5495f  PASS    ami-01c61148c8b35e5d7  9.6.20260210-0
OPP EMEA x86_64  628c9df3-0254-4f91-bc1f-8619d1b8eaa8  PASS    ami-09b73b010580beb08  9.6.20260210-0
OCP arm64        abc249f8-7440-45f7-a4b1-c026baff64c1  FAIL                           no published AMI in band [9.2, 10.2] out of 6 candidate(s)
OKE arm64        d2d3ebcd-c1ca-43d8-bf0a-530433200f35  FAIL                           no published AMI in band [9.2, 10.2] out of 6 candidate(s)
OPP arm64        be6d3e94-c8dc-4a3e-9218-4b449b11f06f  FAIL                           no published AMI in band [9.2, 10.2] out of 6 candidate(s)
E0803 15:40:03.167602 1281403 run.go:72] "command failed" err="3 of 9 product codes failed the skew band check"
make: *** [Makefile:160: check-aws-marketplace-skew] Error 1

The failure above for ARM64 variants is expected: no AMIs with RHEL aligned versions have been published for them(as of writing), and as a result they are not suitable candidates for the band check - the MCO will not use them to perform boot image updates.

Summary by CodeRabbit

  • New Features

    • Added a command to check AWS Marketplace AMI version skew across supported products.
    • Supports configurable AWS region, profile, branch, and table or JSON output.
    • Reports matching AMIs, historical version limits, installer ceilings, diagnostics, and pass/fail status.
    • Added a Make target to build and run the checker with optional arguments.
  • Documentation

    • Added usage instructions, supported products, authentication requirements, flags, and exit-status details.
  • Refactor

    • Centralized Marketplace product and version handling for consistent boot-image processing.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 3, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

@djoshy: This pull request references MCO-2411 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

- What I did

Marketplace-published RHCOS boot images can drift from what MCO supports without any alerting today. This tool will help in alerting the MCO team when the drift is larger than expected.

  • Extracts pkg/controller/bootimage/marketplace fromaws_helpers.go (shared by the controller and the tool).
  • Adds devex/cmd/check-aws-marketplace-skew (make check-aws-marketplace-skew), checks published Marketplace AMIs per product code against MCO's boot-image skew band, fetching both bounds live from GitHub (no local checkout needed).

This is to be run manually by an engineer or an AI agent and not designed to be a Prow periodic.

- How to verify it
AWS marketplace tests should continue to pass, the refactor should have no effect on the functionality of this feature.

When the new target is run locally(assuming AWS and GitHub tokens have been set up), the output should look like so:

$ make check-aws-marketplace-skew
WHAT_PATH=devex/cmd/check-aws-marketplace-skew WHAT=check-aws-marketplace-skew GOTAGS="" hack/build-go.sh
Using version from git...
Building github.com/openshift/machine-config-operator/devex/cmd/check-aws-marketplace-skew (93c54c90, 93c54c909097ff2451e5bdf38c2cfc5fc2977355) for linux/amd64
Skew-limit floor: RHCOS 9.2 (OCP 4.13.0)
Installer ceiling (arm64): 10.2
Installer ceiling (x86_64): 10.2

PRODUCT          PRODUCT ID                            RESULT  MATCHED AMI            DETAIL
OCP x86_64       59ead7de-2540-4653-a8b0-fa7926d5c845  PASS    ami-0b9620e51a0f7930b  9.6.20260210-0
OKE x86_64       963b36c3-de6f-48ed-b802-2b38b2a2cdeb  PASS    ami-0d73ab1083b42d01d  9.6.20260210-0
OPP x86_64       f5da01a6-d046-487c-9072-42fe53b1cad4  PASS    ami-0cffc6b4f37f87305  9.6.20260210-0
OCP EMEA x86_64  962791c7-3ae5-46d1-ba62-c7a5ebac54fd  PASS    ami-09d9a5aa0051b53ce  9.6.20260210-0
OKE EMEA x86_64  7026c8d7-392c-4010-b93c-f93f7bc5495f  PASS    ami-01c61148c8b35e5d7  9.6.20260210-0
OPP EMEA x86_64  628c9df3-0254-4f91-bc1f-8619d1b8eaa8  PASS    ami-09b73b010580beb08  9.6.20260210-0
OCP arm64        abc249f8-7440-45f7-a4b1-c026baff64c1  FAIL                           no published AMI in band [9.2, 10.2] out of 6 candidate(s)
OKE arm64        d2d3ebcd-c1ca-43d8-bf0a-530433200f35  FAIL                           no published AMI in band [9.2, 10.2] out of 6 candidate(s)
OPP arm64        be6d3e94-c8dc-4a3e-9218-4b449b11f06f  FAIL                           no published AMI in band [9.2, 10.2] out of 6 candidate(s)
E0803 15:40:03.167602 1281403 run.go:72] "command failed" err="3 of 9 product codes failed the skew band check"
make: *** [Makefile:160: check-aws-marketplace-skew] Error 1

The failure above for ARM64 variants is expected: no AMIs with RHEL aligned versions have been published for them(as of writing), and as a result they are not suitable candidates for the band check - the MCO will not use them to perform boot image updates.

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.

@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown

Walkthrough

The change adds a Marketplace skew-checking CLI, GitHub and AWS data retrieval, report formats, and shared Marketplace AMI helpers. Boot image controllers now use the shared parsing and comparison logic.

Changes

Marketplace skew validation

Layer / File(s) Summary
Shared Marketplace parsing and controller integration
pkg/controller/bootimage/marketplace/*, pkg/controller/bootimage/aws_helpers.go, pkg/controller/bootimage/ms_helpers.go, pkg/controller/bootimage/platform_helpers.go
Shared helpers now provide Marketplace product lookup, AMI parsing, version comparison, and pre-RHEL-aligned detection. Boot image controller code uses these helpers.
GitHub history and installer ceilings
devex/cmd/check-aws-marketplace-skew/github.go, devex/cmd/check-aws-marketplace-skew/skewlimit.go, devex/cmd/check-aws-marketplace-skew/installerceiling.go, devex/cmd/check-aws-marketplace-skew/*_test.go
The checker retrieves GitHub commit history and raw files, reconstructs historical skew limits, and calculates installer ceilings for supported architectures.
Marketplace AMI evaluation
devex/cmd/check-aws-marketplace-skew/marketplace.go, devex/cmd/check-aws-marketplace-skew/products.go, devex/cmd/check-aws-marketplace-skew/marketplace_test.go
The checker queries Marketplace AMIs, filters versions by an inclusive band, selects the highest match, and creates deterministic product specifications.
CLI orchestration and reporting
devex/cmd/check-aws-marketplace-skew/main.go, devex/cmd/check-aws-marketplace-skew/report.go, Makefile, devex/cmd/check-aws-marketplace-skew/README.md
The command combines all checks, writes table or JSON output, returns failures, and exposes a Make target with usage and operational documentation.

Estimated code review effort: 4 (Complex) | ~45 minutes

Sequence Diagram(s)

sequenceDiagram
  participant CLI
  participant GitHub
  participant AWS
  participant Report
  CLI->>GitHub: retrieve historical skew limits and installer metadata
  GitHub-->>CLI: source revisions and release ceilings
  CLI->>AWS: query Marketplace AMIs
  AWS-->>CLI: AMI metadata
  CLI->>Report: write table or JSON results
Loading

Suggested reviewers: cheesesashimi, isabella-janssen


Important

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

❌ Failed checks (1 error, 1 warning)

Check name Status Explanation Resolution
No-Sensitive-Data-In-Logs ❌ Error cli.Run logs runtime errors, and marketplace.go embeds raw aws arguments and exitErr.Stderr; credential-helper or endpoint errors may expose secrets or internal hostnames. Do not log raw AWS arguments or stderr. Return a sanitized error with the exit status and a safe, allowlisted diagnostic.
Docstring Coverage ⚠️ Warning Docstring coverage is 64.29% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (13 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main change: adding an AWS Marketplace AMI band check target.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed The PR adds no Ginkgo declarations. Its Go tests use static Test and t.Run names, with no timestamps, UUIDs, pod, node, namespace, or IP values.
Test Structure And Quality ✅ Passed The PR adds only standard Go tests using testing.T and testify. No Ginkgo It blocks, cluster resources, or Eventually/Consistently waits are present; httptest cleanup uses t.Cleanup.
Microshift Test Compatibility ✅ Passed The PR adds no Ginkgo e2e tests. New tests use Go's standard testing package, so MicroShift API compatibility checks do not apply.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The pull request adds only standard Go unit tests and CLI code; it adds no Ginkgo e2e tests or multi-node cluster assumptions, so SNO compatibility is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed The full PR adds a CLI, Make target, and Marketplace parsing helpers; it adds no manifests or scheduling constraints such as affinity, topology spread, selectors, tolerations, replicas, or PDBs.
Ote Binary Stdout Contract ✅ Passed Not an OTE binary: the command uses Cobra and is manually invoked via Make; stdout is an intentional table or JSON report, and klog defaults to stderr.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed Changed tests use Go testing/testify, not Ginkgo e2e. The only HTTP test uses a local httptest.Server; no IPv4 literals or public endpoints occur.
No-Weak-Crypto ✅ Passed The changed code uses no weak-crypto APIs or custom cryptography; GITHUB_TOKEN is only sent as an HTTPS Bearer header, and compared values are public version tokens.
Container-Privileges ✅ Passed The PR adds only Makefile, Go, and README files; no container/Kubernetes manifests or prohibited privilege settings appear in the diff. The Make target runs a local binary.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@openshift-ci

openshift-ci Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: djoshy

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:

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 3, 2026
@djoshy djoshy changed the title MCO-2411: Add aws marketplace periodic target MCO-2411: Add AWS marketplace AMI band check target Aug 3, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4

🧹 Nitpick comments (2)
devex/cmd/check-aws-marketplace-skew/github.go (2)

47-73: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Consider extracting shared request/response handling.

fetchRawGitHubFile and fetchGitHubCommitsPage both build a request, call http.DefaultClient.Do, check status codes, and read the body with nearly identical error wrapping. Extracting a small doGitHubRequest(ctx, url, headers) ([]byte, int, error) helper would remove this duplication and centralize the 404/500 handling in one place, which also makes the RefNotFoundError fix above easier to apply consistently.

Also applies to: 100-139

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@devex/cmd/check-aws-marketplace-skew/github.go` around lines 47 - 73, Extract
the duplicated request execution, response-body reading, and error wrapping from
fetchRawGitHubFile and fetchGitHubCommitsPage into a shared doGitHubRequest(ctx,
url, headers) helper returning the response body and status code. Update both
callers to use this helper while preserving their existing URL-specific
behavior, including consistent RefNotFoundError handling and non-success status
reporting.

48-48: 🎯 Functional Correctness | 🔵 Trivial | 💤 Low value

Escape URL path segments before interpolation.

fmt.Sprintf(githubRawURLTemplate, owner, repo, ref, path) (Line 48) and fmt.Sprintf(githubCommitsAPITemplate, ...) (Line 101) interpolate ref and path directly into the URL without url.PathEscape/url.QueryEscape. Current call sites use safe values, but a branch name or path containing characters like #, ?, or a space would break the request silently or hit the wrong resource. Escaping these segments is a small, defensive change.

Also applies to: 101-101

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@devex/cmd/check-aws-marketplace-skew/github.go` at line 48, Update the URL
construction around the raw-content request and the commits API request to
escape interpolated ref and path segments before applying githubRawURLTemplate
and githubCommitsAPITemplate. Use path-segment escaping appropriate for URL
paths, preserving the existing owner/repo structure and request behavior for
ordinary values.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@devex/cmd/check-aws-marketplace-skew/github_test.go`:
- Around line 96-116: Replace require.NoError with assert.NoError for w.Write
errors in the handlers of TestGithubCommitsForPath_paginatesUntilShortPage,
TestGithubCommitsForPath_capsAtMaxPages, and
TestGithubCommitsForPath_branchNotFound, keeping the existing error checks
otherwise unchanged.

In `@devex/cmd/check-aws-marketplace-skew/github.go`:
- Around line 35-43: The RefNotFoundError message incorrectly attributes every
raw GitHub 404 to a missing branch. Update fetchRawGitHubFile to return a
neutral error that includes the requested path, while preserving distinct
handling for the commits endpoint where a missing path yields an empty result;
adjust RefNotFoundError only if needed to support this behavior.

In `@devex/cmd/check-aws-marketplace-skew/main.go`:
- Around line 25-30: Update the root command execution flow around rootCmd and
its RunE handler to create a signal-aware context with an appropriate timeout
before invoking run. Pass that derived context instead of context.Background(),
ensuring cancellation propagates to AWS subprocesses and GitHub requests and the
deadline is released when execution completes.

In `@devex/cmd/check-aws-marketplace-skew/report.go`:
- Around line 28-50: Update Report.WriteTable to return errors and check every
fmt.Fprintf, fmt.Fprintln, and tabwriter.Flush call, returning the first failure
instead of discarding it. At the caller in run, propagate the WriteTable error
so main.go returns failure when output writing is incomplete.

---

Nitpick comments:
In `@devex/cmd/check-aws-marketplace-skew/github.go`:
- Around line 47-73: Extract the duplicated request execution, response-body
reading, and error wrapping from fetchRawGitHubFile and fetchGitHubCommitsPage
into a shared doGitHubRequest(ctx, url, headers) helper returning the response
body and status code. Update both callers to use this helper while preserving
their existing URL-specific behavior, including consistent RefNotFoundError
handling and non-success status reporting.
- Line 48: Update the URL construction around the raw-content request and the
commits API request to escape interpolated ref and path segments before applying
githubRawURLTemplate and githubCommitsAPITemplate. Use path-segment escaping
appropriate for URL paths, preserving the existing owner/repo structure and
request behavior for ordinary values.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: cc243c8a-67ca-4f18-94c2-c098b1880b7c

📥 Commits

Reviewing files that changed from the base of the PR and between 650850c and 93c54c9.

📒 Files selected for processing (19)
  • Makefile
  • devex/cmd/check-aws-marketplace-skew/README.md
  • devex/cmd/check-aws-marketplace-skew/github.go
  • devex/cmd/check-aws-marketplace-skew/github_test.go
  • devex/cmd/check-aws-marketplace-skew/installerceiling.go
  • devex/cmd/check-aws-marketplace-skew/installerceiling_test.go
  • devex/cmd/check-aws-marketplace-skew/main.go
  • devex/cmd/check-aws-marketplace-skew/marketplace.go
  • devex/cmd/check-aws-marketplace-skew/marketplace_test.go
  • devex/cmd/check-aws-marketplace-skew/products.go
  • devex/cmd/check-aws-marketplace-skew/report.go
  • devex/cmd/check-aws-marketplace-skew/skewlimit.go
  • devex/cmd/check-aws-marketplace-skew/skewlimit_test.go
  • pkg/controller/bootimage/aws_helpers.go
  • pkg/controller/bootimage/aws_helpers_test.go
  • pkg/controller/bootimage/marketplace/marketplace.go
  • pkg/controller/bootimage/marketplace/marketplace_test.go
  • pkg/controller/bootimage/ms_helpers.go
  • pkg/controller/bootimage/platform_helpers.go
💤 Files with no reviewable changes (1)
  • pkg/controller/bootimage/aws_helpers_test.go

Comment thread devex/cmd/check-aws-marketplace-skew/github_test.go
Comment thread devex/cmd/check-aws-marketplace-skew/github.go Outdated
Comment thread devex/cmd/check-aws-marketplace-skew/main.go
Comment thread devex/cmd/check-aws-marketplace-skew/report.go Outdated
@djoshy
djoshy force-pushed the add-aws-marketplace-periodic-target branch from 93c54c9 to 3f1c874 Compare August 7, 2026 17:32

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@devex/cmd/check-aws-marketplace-skew/github.go`:
- Around line 162-165: Validate each raw commit’s SHA and committer date in the
loop that builds commits before appending a ghCommit. If either field is empty
or missing, return an error instead of emitting a zero-value or incomplete
record; preserve the existing conversion for valid records.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: a7bedfaa-cc57-4e7b-b93a-d0da49fcde18

📥 Commits

Reviewing files that changed from the base of the PR and between 93c54c9 and 3f1c874.

📒 Files selected for processing (5)
  • devex/cmd/check-aws-marketplace-skew/github.go
  • devex/cmd/check-aws-marketplace-skew/github_test.go
  • devex/cmd/check-aws-marketplace-skew/main.go
  • devex/cmd/check-aws-marketplace-skew/marketplace.go
  • devex/cmd/check-aws-marketplace-skew/report.go
🚧 Files skipped from review as they are similar to previous changes (3)
  • devex/cmd/check-aws-marketplace-skew/main.go
  • devex/cmd/check-aws-marketplace-skew/github_test.go
  • devex/cmd/check-aws-marketplace-skew/marketplace.go

Comment thread devex/cmd/check-aws-marketplace-skew/github.go
@djoshy

djoshy commented Aug 7, 2026

Copy link
Copy Markdown
Contributor Author

/retest-required

1 similar comment
@djoshy

djoshy commented Aug 7, 2026

Copy link
Copy Markdown
Contributor Author

/retest-required

@openshift-ci

openshift-ci Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

@djoshy: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/perfscale-control-plane-6nodes 3f1c874 link false /test perfscale-control-plane-6nodes

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants