This repository was archived by the owner on Mar 25, 2024. It is now read-only.
Add Secret config fields to vSphere cloud provider #1165
Conversation
This file contains hidden or 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
nikkelma
changed the title
nikkelma
changed the title
nikkelma
force-pushed
the
vsphere-cloud-provider-secret
branch
from
4697362 to
2e4cd90
Compare
nikkelma
changed the title
nikkelma
force-pushed
the
vsphere-cloud-provider-secret
branch
from
2e4cd90 to
035ec1a
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Add support for
secret-nameandsecret-namespaceto all related vSphere cloud provider configuration types.