Re-running gitlabform with changes to jira services doesn't apply any change

[Dridge]

Re-running gitlabform with changes to jira services doesn't apply any change

[gdubicki]

Hi @Dridge !

gitlabform just goes through each service defined in this config sections and makes PUT requests to GitLab API. So both password change and commit events change flag flip should work.

But I have checked that and it seems that there is a bug in GitLab API that makes those PUT requests not work, at least for JIRA service.

We could try a workaround of deleting and recreating services with API on each gitlabform run but I am afaid of the side effects (and a bit about performance). I have quickly tried making a diff between current and target service config (or, to be precise, a check for target config being subset of the current config) to check if a PUT request is needed but for example for Jira service the GitLab API does not return password in response (which make sense, of course) what makes this diffing ineffective. Maybe we should make this "always recreate services" a default off feature (or rather a workaround)?

[Dridge]

Maybe we should make this "always recreate services" a default off feature

This sounds reasonable to me, and the only way to get around the gitlab api bug.

[gdubicki]

My new integrations tests (see link above) confirm that there is this problem, most probably with all services (I tested using the first one alphabetically, asana).

[gdubicki]

I noted in https://gitlab.com/gitlab-org/gitlab/-/issues/202216 that the password field is not being updated too.

[gdubicki]

I have just released v1.13.4 with the "recreate" flag mentioned a few comments above.

See this example config section for info how to use it: https://github.com/egnyte/gitlabform/blob/master/config.yml#L179-L183

Please let me know if this helps, @Dridge .

[gdubicki]

Thanks to Vincent Bisserié's help (if you are reading this - thank you!) I fixed the root cause and released v1.13.5 where this issue should be completely resolved without any workarounds.

Please reopen this issue if it does not help you, @Dridge .