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 projects. The other project gets (in the UI) a section called: "Deploy keys from projects you have access to" that shows the server key that was added to the first project and has a button to click to enable it on the second as well.
If attempting to have matching deploy key resources to both projects, the following error occurs:
Error: gitlab_deploy_key::create: gitlab_deploy_key::create: #<Net::HTTPBadRequest 400 Bad Request readbody=true>
Error: /Stage[main]/Profile::Pe::Master/Git_deploy_key[add_deploy_key_to_hieradata]/ensure: change from absent to present failed: gitlab_deploy_key::create: gitlab_deploy_key::create: #<Net::HTTPBadRequest 400 Bad Request readbody=true>
The simple workaround is to go into the UI and click the button, but I wanted to raise it in case someone knew an easy way to extend the provider to handle this case.
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 projects. The other project gets (in the UI) a section called: "Deploy keys from projects you have access to" that shows the server key that was added to the first project and has a button to click to enable it on the second as well.
If attempting to have matching deploy key resources to both projects, the following error occurs:
Error: gitlab_deploy_key::create: gitlab_deploy_key::create: #<Net::HTTPBadRequest 400 Bad Request readbody=true>
Error: /Stage[main]/Profile::Pe::Master/Git_deploy_key[add_deploy_key_to_hieradata]/ensure: change from absent to present failed: gitlab_deploy_key::create: gitlab_deploy_key::create: #<Net::HTTPBadRequest 400 Bad Request readbody=true>
The simple workaround is to go into the UI and click the button, but I wanted to raise it in case someone knew an easy way to extend the provider to handle this case.