Credentials Provider?

[ericblade]

What feature do you want to see added?

Any possibility of this being upgraded to being a proper Credentials Provider for Jenkins, as Azure has a plugin for? I know there's not a lot of them out there, but this feature is pretty much mandatory to be able to use this plugin with a lot of other Jenkins functionality.

Upstream changes

No response

Are you interested in contributing this feature?

No response

[averymd]

This would be super duper helpful. I spent a while trying to get all my jobs to pull down and use copies of the CLI tool in my pipelines and freestyle builds before giving up the hassle and going back to native Jenkins credentials. (I have multiple agents with different architectures, so there's more logic required than in the standard example.)

I have to touch every job and have to pull specific versions of the CLI tool in each job (i.e., there's no "latest" version) instead of migrating smoothly from Jenkins' store while keeping existing pipeline environment settings and withCredentials calls.

It's definitely prohibitive, and I say this as someone who runs 1Password Connect and uses the 1Password integrations for Ansible and python (vanilla, Django, and Flask) extensively. I am fully in the ecosystem. 😸

[ericblade]

My current corporate environment has approved 1Pass for use with Jenkins, and we'd really like to use it, and we're trying to build a system where we can nab all the credentials needed throughout Jenkins from it, so we don't have to use Jenkins internal store -- because Jenkins internal store is completely useless if you are trying to build a proper and repeatable container stack.

Therefore, we really need this. :-)

[mihaiplesa]

Same here, would love to have this functionality.

[utobi]

+1

[Minreaux]

Agree with everyone else here. A credentials provider implementation for this plugin is needed for it to be viable to use this plugin in a production Jenkins instance that is managed entirely as code.

Without it, you can use credentials stored in 1Password for pipelines, but you cannot use any 1Password-stored credentials for system-level Jenkins things (i.e. a credential to login to GitHub to automatically pull a pipeline Jenkinsfile into your Jenkins instance).

[quacktacular]

+1