Gregory Dosh

Talking with @wass3r and hypothesizing it's URL encoding issues, and testing this seems to confirm. It also happens when a name starts with "?" too. ```sh vela remove secret --org...

The scope of this issue is a little vague since I can think of two different issues it's trying to address. It could be trying to address the scope of...

The issue with the template system is mostly with name collisions of steps getting duplicated and failing to run because of the re-use of templates. That should absolutely get fixed,...

My small comment would be to point slightly back at my original comment in https://github.com/go-vela/community/issues/62#issuecomment-987119653. I don't quite know what "improved security and access control" is aiming at, if it's...

@kneal I think that is what I'm trying to understand from the original issue. - improved security and access control - Improved how? What security issue is of concern here?...

I think this is the confusion is in how I described my idea. The way I was thinking about it would solve the " help us in cases where an...

That's exactly what I was trying to (poorly) articulate. The trouble I can see from my idea would be in articulating to users why secrets weren't available for their particular...

@wass3r I'm sure I'm using the terms inappropriately, ACL & RBAC etc. I'm mostly trying to convey that we use the SCM permission already in place like we do for...

In a competitive CI landscape adding even one additional step or requirement on end users will probably push them away from your product. Be sure to keep that in mind...

@laxmanpradhan Thanks for the initial discovery and pointers in the right direction. The missing piece might just be volume mounting over the top of the `sites-enabled` path too. I got...