Add authorization mechanics for Jenkins as a Code.

[fordagame]

trafficstars

Hello,

In jenkins as a code plugin, we want to load jenkins.yaml file with configuration from bitbucket repository. We encounter one problem. Authenthication in bitbucket is done through Authorization headers. Unfortunately right now jenkins as a code is not supporting adding any headers or authorization information for yamlsource as url. Solution of this problem right now can be found in this fork: https://github.com/matankatz/configuration-as-code-plugin/commit/5bc8a7fa3b55ef59c2973e82dd43730cc1df8c97

Can we add this to jenkins, because it is really very useful and needed feature if you don't want to host static yaml file.

[ewelinawilkosz]

was this issue discussed anywhere? Or is there another way to solve the problem - I've seen many people interested in having a solution for authorisation

[jetersen]

@ewelinawilkosz This falls back to #34 #1365 #273

[jetersen]

I would really like for a more extensible configuration source. We could add the scm-api to support the various scm plugins such as the git plugin.

[ewelinawilkosz]

thanks for the update when it comes to e.g. bitbucket an actual support for repo, not just the url, would be a huge improvement, so you can point out a folder, not a file only. and specific branch etc... but maybe I should go through the issues you have mentioned above before letting my imagination free :)

[y0zg]

any update on this feature please?

[timja]

There was a pull request here which wouldn't take someone a lot of work to revive and get it merged: https://github.com/jenkinsci/configuration-as-code-plugin/pull/665