Closed adithyagokhale closed 1 year ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen
.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Exclude this issue from closing again by commenting /lifecycle frozen
.
/close
@openshift-bot: Closing this issue.
I have a use case where I want to authorize based on the request parameters in the path. For example: Following path matches when the HTTP URL is "/entities/sample_context?action=summarize" -openshift-delegate-urls={"/entities":{"namespace":"test","resource":"services","verb":"get"}}
If I want to restrict few users to execute only few action parameters above, how can I add the path ? For Example, I dont want certain users to execute "/entities/sample_context?action=delete".
Is it possible to achieve this behavior ?