Refine mandatory location checking logic
Update `ConfigDataEnvironment.checkMandatoryLocations` to use the actual locations that were imported, including those that were skipped because the related `ConfigDataResource` had already been imported by a different location. Prior to this commit, any location that was skipped because it had already been imported would throw a `ConfigDataNotFoundException`. Closes gh-26147 Co-authored-by:Scott Frederick <sfrederick@vmware.com> Co-authored-by:
Madhura Bhave <mbhave@vmware.com>
Showing
Please register or sign in to comment