-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(policy): apply dynamic policy #188
Conversation
c585c1a
to
6f81e89
Compare
9a5f0f1
to
161b9f0
Compare
161b9f0
to
78ee4c8
Compare
b18752e
to
d52021d
Compare
@@ -3656,6 +3681,9 @@ | |||
"permissions": { | |||
"type": "array", | |||
"items": {} | |||
}, | |||
"type": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we still need this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wait, I did not add this but it came up on this PR
this is the proton for policy changes goto/proton#139
and looks like this field was introduced on this PR https://github.com/goto/proton/pull/138/files
tried to rebase but it says it's already updated hmm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh I guess this one got added on proton by gtf but currrently not implemented on our guardian. That's why on my addition of new param, it also got added there. This should be ok for now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let’s make sure it doesn’t break anything.
No description provided.