-
Notifications
You must be signed in to change notification settings - Fork 9.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
provider/gitlab: add gitlab_deploy_key
#14734
provider/gitlab: add gitlab_deploy_key
#14734
Conversation
Todo:
To expand on that pending merge request, the /v3 api cannot currently manage the
Terraform will repeatedly delete and recreate the deploy key. The merge request will fix that, but will take integration and releasing. |
Here we extend the gitlab provider further by adding a `gitlab_deploy_key` resource. This resource allows management of a projects deploy keys.
017576a
to
3245071
Compare
I've split out a commit to remove the testing of the |
gitlab_deploy_key
gitlab_deploy_key
Here we remove the testing of the `can_push` attribute. This makes the tests less comprehensive, but will allow them to work with the current release of gitlab-ce. This change is staged as a distinct commit so it can be easily dropped/reverted once gitlab MR !11607 has reached a released state. https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/11607
9d5a04e
to
af7c5cb
Compare
Hi @richardc I agree with your move to remove that param for now - we should just document this as a NOTE on the resource - to say that it can't currently be managed (not the reason) and then tell the user what gitlab defaults to Sound ok? Paul |
@stack72 So just patch website/source/docs/providers/gitlab/r/deploy_key.html.markdown to indicate the attribute isn't fully functional? I don't see a mechanism to do this in the code from a skim of schema.Schema. |
@richardc yeah there is no formal way to do this. The Markdown looks as follows
|
Note that the can_push attribute of gitlab_deploy_key doesn't currently work. This note can be removed once https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/11607 is merged and in general circulation.
@stack72 How's the wording on that? |
Hi @richardc This works - if it's not clear to users, we can change it up :) Thanks for this! Tests are green as expected:
Paul |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
As suggested in #14471 this adds a
gitlab_deploy_key
resource to manage deploy keys.