Ability to express "Enable Agent → Master Access Control" in configuration about configuration-as-code-plugin HOT 9 CLOSED

we could rely on AdminWhitelistRule#setMasterKillSwitch(), but need some way to define a yaml path to this extension. We can't just expose all extensions, need to define which ones have to be included and how to.

I wonder why AdminWhitelistRule is not exposed as a ManagementLink or something similar. I don't even know how one access it's configuration UI, can't find this in UI menus

from configuration-as-code-plugin.

ok, this is actually managed by jenkins.security.s2m.MasterKillSwitchConfiguration without an explicit setter and manual databinding. So can't be supported out-of-the-box and will require some glue code (or fix in core)

from configuration-as-code-plugin.

The UI is in "Configure Global Security/Enable Agent → Master Access Control"

from configuration-as-code-plugin.

yes, indeed. But this UI is exposed by MasterKillSwitchConfiguration which delegates to AdminWhitelistRule. There's few places where such a pattern applies, mostly for backward compatibility. I think we should get some @ManagedBy or @DelegateTo annotation to document this and make this discoverable by introspection.

from configuration-as-code-plugin.

I was referring to your comment that you could not find it in the UI menus.
I understand it requires some changes in core. This is why I raised this issue instead of creating PR (: . Regards,
Ohad

from configuration-as-code-plugin.

Working on it, important for remoting

from configuration-as-code-plugin.

It would be great to merge it for jenkinsci/jenkins#2930

from configuration-as-code-plugin.

@odavid Created #90

from configuration-as-code-plugin.

Thanks @oleg-nenashev.

from configuration-as-code-plugin.