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

Make generateSecret more robust #393

Merged
merged 1 commit into from
Nov 7, 2023

Conversation

morgen-peschke
Copy link
Contributor

@morgen-peschke morgen-peschke commented Oct 24, 2023

  1. Handle non-200 successes
  2. Attempt recovery if the body is malformed/omitted

Addresses #392

1. Handle non-200 successes
2. Attempt recovery if the body is malformed/omitted

test(
"generateSecret works as expected when receiving a 200 Ok with an unparsable response"
) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm lost what made that test unparsable.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The third type argument to generateSecret on line 697 doesn't match the second, so it's putting in a SelfManaged and trying to pull it back out as a VaultKeys (which has an incompatible serialization).

@morgen-peschke morgen-peschke merged commit 76b7aa8 into main Nov 7, 2023
13 checks passed
@morgen-peschke morgen-peschke deleted the ISSUE-392-increase-generate-secret-robustness branch November 7, 2023 19:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants