Browse Source
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>pull/26435/head
5 changed files with 29 additions and 5 deletions
Loading…
Reference in new issue