When extending VaultConfigDataLoader and VaultConfigDataLocationResolver for customized development, I encountered some obstacles. Certain methods in these classes are set to private, making it impossible to reuse existing logic or override specific behaviors when inheriting these classes.
To enable more flexible extensibility, I suggest changing the access modifiers of these methods from private to protected or public.
If this suggestion is accepted, I am willing to create a merge request for this change.