In a previous setup we used the GoCD APIs triggered by a simple scripted
curl-oriented pipeline within GoCD itself, similar to how Aravind suggests.
In that specific case the "synchronize group permissions" pipeline was
manually triggered by an admin on request, but there would have been
different
Tricky. Yes, there is no mechanism I'm aware of to set default permissions
for new pipeline groups. :(
For the existing groups and your upcoming upgrade, I would suggest making
the implicit permission explicit, by adding a role permission to the 230
pipeline groups, and then giving that role view
Hi everyone,
We are working on upgrading from GoCD 19.8.0 to the current version. One of
the major changes we need to account for is the default permissions on
pipeline groups.
In 19.8.0, pipelines are open by default, i.e., if there are no permissions
explicitly defined for a pipeline group,
