Autoload default config profiles into ServerInstances. #5226
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.
The recent commit #5118 introduced the ability to select and add OCI profiles, but damaged the Cloud Explorer for Apache Netbeans VSCode extension - it relied on the (default) OCI profile to be automatically converted into
ServerInstance
.This PR adds an alternative mode, which can be enabled using Branding API, that automatically loads all profiles from the default OCI configuration into the Cloud explorer (in NB IDE or vscode). In the future additional profiles from custom configuration can be added when the Add Cloud / Oracle wizard is enhanced to support custom configs.
NetBeans IDE behaves as in #5118, for the user convenience, vscode extension loads profiles from the default config.