Fixes #36750 - Add aggregated CV version content counts to count field and return via API #10746
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What are the changes introduced in this pull request?
Adds aggregated cv_version content count to smart proxy content counts and adds the content counts to API.
Considerations taken when implementing this change?
We need aggregated cv_version content counts to easily display on UI and the aggregated count on the API is good information to have about the synced CV version.
What are the testing steps for this pull request?
Add some repositories of different content types to the CV and publish and promote to an env tied to a smart proxy.
Check the API call for smart_proxy/:id.. You can check this in the network tab when you go to smart proxy details page.
The API return should have a cv_version_content_counts key with aggregated counts of all content types.