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

Backport of Fix non-deterministic ordering of 'required' field in OpenAPI spec into release/1.13.x #20905

Conversation

hc-github-team-secure-vault-core
Copy link
Contributor

Backport

This PR is auto-generated from #20881 to be assessed for backporting due to the inclusion of the label backport/1.13.x.

The below text is copied from the body of the original PR.


Fixes a minor annoyance I discovered whilst comparing before and after
OpenAPI specs whilst working on hashicorp/vault-client-go#180.

Sort the entries in a JSON array which has set semantics, after we
construct it by iterating a map (non-deterministic ordering).


Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/deterministic-openapi-order/strongly-pleasant-malamute branch 2 times, most recently from 38471bb to 1b25ff8 Compare May 31, 2023 19:10
@averche averche enabled auto-merge (squash) May 31, 2023 19:12
@averche averche merged commit 6daa1bd into release/1.13.x May 31, 2023
@averche averche deleted the backport/deterministic-openapi-order/strongly-pleasant-malamute branch May 31, 2023 19:46
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