-
Notifications
You must be signed in to change notification settings - Fork 284
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
chore(sdf, dal): Cleanup old pre-REBAC routes #5247
base: main
Are you sure you want to change the base?
Conversation
Dependency Review✅ No vulnerabilities or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Files |
path: () => "/change_set/begin_abandon_approval_process", | ||
force_apply: { | ||
path: (vars: ROUTE_VARS) => | ||
`/v2/workspaces/${vars.workspaceId}/change-sets/${vars.changeSetId}/force_apply`, | ||
method: "POST", | ||
}, | ||
begin_approval_process: { |
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.
are we using this still? or can this one get cleaned up?
Way back when, I was considering keeping the low-fi approval flow for things like 'abandon change set' (as it gives people who are on the change set a chance to stop the abandon if they're actively doing something) but wasn't totally sure...
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.
I do see that an endpoint still is called so I left it in place - it's when the user is an approver or an owner and they force their own approval
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.
Sorry bad github comment location - I meant the begin_approval_process
pieces
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.
Definitely not for this PR - just leaving a note that we need to update both this client and the tests to account for views when we clean up that feature flag
No description provided.