amimas
amimas
Closing this issue. As per discussions above, it may have been an issue in earlier gitlab versions. Nothing to do with gitlabform.
Curious what happens if it's set to `rootgroup/*`
Thanks for clarifying. I always use `ALL DEFINED` when executing gitlabform. And I use different config file for different groups. It might not help, but thought I'd mention in case...
> Is there a way to tell that I want the gitlab form configuration be only applied to this specific group (for instance "my_group/" instead of "my_group/*") and not to...
> > > Is there a way to tell that I want the gitlab form configuration be only applied to this specific group (for instance "my_group/" instead of "my_group/*") and...
Sure @nabinbhatt . Welcome and thank you for helping.
@nabinbhatt - were you able to make any progress with this?
@TimKnight-DWP - Do we still need to keep this issue open? If not, let's close it. Also, looks like this was specifically around scheduled pipeline related changes, which has been...
Thanks for the heads up. Would you be able to help with the update? PR is welcome if anyone else can pick this up.
> How do we handle features like this that are only available from a particular GitLab version? I'd say in a backward-compatible way. So, there should be logic to check...