amimas

@dd-ssc - Not sure what brought you to this thread but really glad you commented. Usually I test out features directly in GitLab but somehow I didn't think of it...

I realized that I was a bit too quick to the tests mentioned in previous comment. The environment scope for group variable requires premium or ultimate license. My test gitlab...

Couldn't find an existing issue in GitLab about it. Opened one now: https://gitlab.com/gitlab-org/gitlab/-/issues/548248

Interesting suggestion @mrjesma . How do you normally manage your gitlab runners? In my experience, I've used terraform using the following module that manages runners for an instance or a...

Closing this issue. As I suggested above, managing runners and related setting would be best managed separately as that involves dealing with actual resources (e.g. VMs, Kubernetes, etc.). GitLabForm manages...

> I think we should also allow a frontmatter or config like secret: true, so that if it's not linked from anywhere, it does not warn/error. Sometimes people want a...

Isn't this already doable right now? Even if the warning/error message about orphaned docs feature is implemented, in this case you'd just set that option to be a warning. Not...

I haven't yet come across a use case like this. Would like to understand it more. > It would be great if we can add a property enforce to variables...

Hi, thanks for opening the issue. The problem mentioned in the initial message is a bit unclear. Let's start with a sample gitlabform config you're using and how you execute...

Thanks @hiaik for the details. > Looking at above + logs from gitlab saas, we have found that when protected tags endpoint is called ( tag name "release/*") more than...