Skip to content

WIP: feat: added the initial implementation of the [jenkins] provider#7

Draft
pcanilho wants to merge 1 commit intoisometry:mainfrom
pcanilho:feature/provider-jenkins
Draft

WIP: feat: added the initial implementation of the [jenkins] provider#7
pcanilho wants to merge 1 commit intoisometry:mainfrom
pcanilho:feature/provider-jenkins

Conversation

@pcanilho
Copy link
Contributor

@pcanilho pcanilho commented Apr 3, 2024

No description provided.

@pcanilho pcanilho force-pushed the feature/provider-jenkins branch 4 times, most recently from 9bc691f to 6b149e3 Compare April 3, 2024 20:29
credential objects which aims at populating the `username` and `token` fields. Multiple credentials providers can be used.
If multiple credentials providers are used, the `username` and `token` fields are populated by merging the provider results.

## Credentials provider support
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I love the idea, but I'm a little wary of re-using the "provider" terminology here. Maybe "credentials source" rather than "credentials provider", e.g. "Supported Credentials Sources"

detail: true
credentials:
- provider: vault
address: https://vault.com
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Were we to add a Vault credentials source, then I think that address would belong in it, rather than per (component-)provider-instance =)

@pcanilho pcanilho force-pushed the feature/provider-jenkins branch from 6b149e3 to e7b58f4 Compare April 4, 2024 05:56
@pcanilho pcanilho force-pushed the feature/provider-jenkins branch from e7b58f4 to 3480375 Compare April 5, 2024 20:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants