feat: Ability to pass in a scope for certificate authentication #154
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.
Attempts to fix #153.
Requires #152 first as this includes the fix for #151.Tested locally with my setup:
I have tested the following other scenarios:
VENAFI_TOKEN
,VENAFI_CLIENT_ID
&VENAFI_SCOPE
explicitly in provider. All works with token.VENAFI_TOKEN
and leave clientID and scope to the code default values. All still works with token.