You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Roadmap 2025/02 Abilty to bind a RemoteUser from another namespace
As an application DevOps, I want to create only one RemoteUser and be able to use it in the RemoteSyncer of other namespaces I have access to.
What to do
First, get a RemoteUserBinding list in all of the namespaces the user has access to. Currently, we get a list of all the RemoteUserBindings that are in the same namespace the RemoteSyncer. This is the hardest part.
Above the line #L161, you need to list the namespace the user has access to. Then create a list of RemoteUserBinding which are in these namespaces. It can be done in one time or in a loop and then concatenate the lists.
Then, use the namespace of the RemoteUser instead of the RemoteSyncer one: replace namespace by ref.Namespace.
Roadmap 2025/02 Abilty to bind a RemoteUser from another namespace
As an application DevOps, I want to create only one RemoteUser and be able to use it in the RemoteSyncer of other namespaces I have access to.
What to do
First, get a RemoteUserBinding list in all of the namespaces the user has access to. Currently, we get a list of all the RemoteUserBindings that are in the same namespace the RemoteSyncer. This is the hardest part.
syngit/internal/controller/webhook_request_checker.go
Line 161 in 0ee6e8d
Above the line #L161, you need to list the namespace the user has access to. Then create a list of RemoteUserBinding which are in these namespaces. It can be done in one time or in a loop and then concatenate the lists.
Then, use the namespace of the RemoteUser instead of the RemoteSyncer one: replace
namespace
byref.Namespace
.syngit/internal/controller/webhook_request_checker.go
Lines 281 to 284 in 0ee6e8d
Additional context
If you have any questions, please tag @damsien.
The text was updated successfully, but these errors were encountered: