Skip to content

Make license sync configurations exclusive

Oscar Tovar requested to merge otovar/make-license-config-versions-exclusive into master

What does this MR do and why?

Make license sync configurations exclusive

The sync service will always use the v2 data ingestion when the compressed data set feature flag is enabled. This opens up the possibility for the ingestion to try to ingest all of the v1 dataset using the v2 ingestion logic, which will result in a lot of error logging and used processing cycles. As a short term fix, the logic for synchronization has changed to make v1 and v2 exclusive at the configuration level. If v2 and v1 are both enabled, then v2 will win and only its configuration will be added.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Oscar Tovar

Merge request reports