Action for adding Cloud Assets sensitive data to Vault #7831
+597
−819
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jhorvath
added
LSP
jhorvath
approved these changes
Oct 8, 2024
enterprise/cloud.oracle/src/org/netbeans/modules/cloud/oracle/vault/VaultItemClient.java
Outdated
Show resolved
Hide resolved
petrovic-d
force-pushed
the
cloud-assets-upload-secrets-from-vault-node
branch
from
67d76ce
to
9cbe9e8
Compare
petrovic-d
force-pushed
the
cloud-assets-upload-secrets-from-vault-node
branch
from
9cbe9e8
to
36af271
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
New action on Vault node in Cloud Assets that will add sensitive data to OCI Vault (currently only DB properties)
Force setting Database Node reference name