Skip to content
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

signer: Pass policy rejections back to the node #484

Merged
merged 2 commits into from
Jul 22, 2024

Conversation

cdecker
Copy link
Collaborator

@cdecker cdecker commented Jul 18, 2024

When the signer rejects a request we had no indication as to what went
wrong until now. With this change we (a) send back the error as if it
were a normal response and then (b) print the error in the logs,
allowing us to collate the operations causing the rejection with the
rejection itself.

@cdecker cdecker force-pushed the 202407-signer-rejection-part2 branch 3 times, most recently from 3e0212f to 423b5f7 Compare July 19, 2024 11:55
@cdecker cdecker enabled auto-merge (rebase) July 19, 2024 11:55
@cdecker cdecker disabled auto-merge July 22, 2024 14:56
@cdecker cdecker force-pushed the 202407-signer-rejection-part2 branch from 423b5f7 to 69fd3d7 Compare July 22, 2024 15:00
@cdecker cdecker enabled auto-merge (rebase) July 22, 2024 15:00
cdecker added 2 commits July 22, 2024 17:25
When the signer rejects a request we had no indication as to what went
wrong until now. With this change we (a) send back the error as if it
were a normal response and then (b) print the error in the logs,
allowing us to collate the operations causing the rejection with the
rejection itself.
@cdecker cdecker force-pushed the 202407-signer-rejection-part2 branch from 69fd3d7 to 26775e9 Compare July 22, 2024 16:07
@cdecker cdecker merged commit c371a5a into main Jul 22, 2024
13 checks passed
@cdecker cdecker deleted the 202407-signer-rejection-part2 branch July 22, 2024 16:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants