abrader-gms
abrader-gms copied to clipboard
abrader
Git management system types and providers for Puppet utilizing Github, Gitlab, Stash APIs
Hey @abrader as it seems from https://github.com/abrader/abrader-gms/pull/44 you are not actively supporting this module anymore, but we need some important fixes in it. Therefore I propose to migrate this module...
- Updated metadata.json (support for newer Puppet and Stdlib) - Fixed Travis - Added Gitlab CI - Incorporated #40 and #47, so this version can now be used again with...
On *GitLab* (Github untested), the git_webhook resource doesn't modify the webhook if it already exists: git_webhook { 'web_post_receive_webhook' : ensure => present, webhook_url => 'http://puppetserver.example.com:8088/payload', token => hiera('gitlab_api_token'), project_name =>...
Gitlab does not work with API/v3, it proposes using v4. And a project can belong to groups organized in a hierarchy with more than one slash in the full path.
Allow requests to the local network from hooks and services is now disabled by default and will cause all custom hooks to fail inside the private network: https://docs.gitlab.com/ee/security/webhooks.html Is it...
The metadata.json file limits this module to only working with versions prior to puppet 6. Please add support for puppet 6.
I'm getting `unexpected token` and I don't know what's wrong. I did everything as documented but doesn't seem to help. Could you please assist? Full errror below. ``` Error: /Stage[main]/Profile::Puppet::R10k/Git_webhook[github_post_receive]:...
OS: Centos 7.5.1804 Module version: v1.0.3 Puppet: v5.5.1 Gitlab: gitlab-ee-11.0.0-ee.0.el7.x86_64 Debug output from failed puppet run. ``` opening connection to gitlab.company.local:443... opened starting SSL for gitlab.company.local:443... SSL established "HTTP/1.1 410...
If you have one master that will be accessing two Gitlab projects (e.g. puppet_control and puppet_hiera), Gitlab will only let you create a deploy key to one of the two...
Hey, as we discussed in #44 and #43 this pull requests adds an gitab_api_version variable so the user can still decide to use the v3 api. I only tested the...