Greg Dubicki

Thanks @ss7548 ! Now please enable running your test by adding a line like https://github.com/egnyte/gitlabform/blob/v2/.github/workflows/acceptance.yml#L33 and make the tests pass. I recommend you updating your test to the newer style,...

Looking at how much time has passed since @ss7548 last reply here, I am afraid that he won't finish it. But the code here looks almost ready, needs only update...

Unfortunately it seems that it's one of the many inconsistencies in the GitLab APIs - although the docs say that you can make the integration active or not (https://docs.gitlab.com/ee/api/services.html#get-jira-service-settings), both...

I tried working around the issue by deleting the active service and creating it anew as inactive but it did not work - service is always created as active.

Maybe that's obvious but as a workaround I would just delete the service (`delete: true`) instead of disabling. Without GitLabForm, using the web UI it makes some sense to disable...

As of now `skip: true` works only for the *whole* sections, so f.e. all branches or all files. We would like to make this more configurable in gitlabform v3, see...

With the `inherit: false` working at any place in the config it could be used as a replacement for `skip: true` **if** we would also add the removal of an...

@amimas : yes, we strive for exactly such way of deprecating syntax - warning first, remove support later.

Hi @Neola! There is no `compliance_frameworks` under https://docs.gitlab.com/ee/api/projects.html#edit-project. It seems that it *was* there but was removed in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/88297 because it did not work. To add support for this we...

Thanks for the fix, @ep-linden ! It has been pre-released in v3 RC3 released today so it also will be fixed in the final v3 that will be released within...