Add "last" element handling in nested arrays #80
Merged
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.
Description
Our cluster-registry integration, for the Edge GW to CGW migration tools, needs monitoring for various client CRs, during the migration process, especially their CR status, but also other parameters as well.
Sometimes the status is an array of statuses, so we would need to monitor only the last status entry, since that's the valid one for us.
We don't have the length for those arrays apriori, so we cannot call the ServiceMetadataWatcher with:
apiVersion: pdm.adobe.io/v1
kind: RequestProcessing
name: maia-e2e-test-rp-mircea
watchedFields:
src: spec.authPolicies[X].policyId
where X is a number, the last in the array, so we would need a "last" string in the watchedFields, to represent the last monitored entry in the array, no matter its length.
This PR adds the "last" string in the CR handling.
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: