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
Seeing the following error when using tw runs view -i.
tower-backend-1 | Dec-11 21:43:44.839 [io-executor-thread-3] 104.28.208.123 DEBUG i.s.t.s.r.AbstractAuthRequiredInterceptor - Operation 'DescribeLaunch' rejected
tower-backend-1 | Request URI: /launch/3pUuGa7dlgQmXb7EoktpKd?workspaceId=40141464937493
tower-backend-1 | Request data: {authenticatedUserId=3, roles=[user], launchId=3pUuGa7dlgQmXb7EoktpKd, workspaceId=40141464937493, sourceWorkspaceId=null}
tower-backend-1 | User scopes: [usr:user, wsp:view]
tower-backend-1 | Context: {scope="usr:user", checkers=[LaunchBelongsToUserChecker], result="Rejected: Launch belongs to a workspace"}
tower-backend-1 | Context: {scope="wsp:owner", checkers=[LaunchBelongsToWorkspaceChecker], result="Rejected: Scope 'wsp:owner' not found among user scopes"}
tower-backend-1 | Context: {scope="wsp:admin", checkers=[LaunchBelongsToWorkspaceChecker], result="Rejected: Scope 'wsp:admin' not found among user scopes"}
tower-backend-1 | Context: {scope="wsp:maintain", checkers=[LaunchBelongsToWorkspaceChecker], result="Rejected: Scope 'wsp:maintain' not found among user scopes"}
tower-backend-1 | Context: {scope="wsp:launch", checkers=[LaunchBelongsToWorkspaceChecker], result="Rejected: Scope 'wsp:launch' not found among user scopes"}
tower-backend-1 | Dec-11 21:43:44.843 [io-executor-thread-9] 104.28.208.123 WARN i.s.t.c.GlobalErrorController - Operation 'DescribeLaunch' not allowed to user 3 with roles usr:user,wsp:view
mark@ubuntu:~/scripts/tw$ ./tw runs view -i 37iBJYsvHoamxx
ERROR: Pipeline run '37iBJYsvHoamxx' not found at [longs / department] workspace
Upgrading the permission to Launch enables the use of the command.
The text was updated successfully, but these errors were encountered:
Seeing the following error when using tw runs view -i.
Upgrading the permission to Launch enables the use of the command.
The text was updated successfully, but these errors were encountered: