Enhancement Request: Provide a fixed order for OpenAPI security responses

[dgf]

Description

We've encountered some challenges while using OpenAPI definitions generated by Quarkus in our CI workflow. Constantly/randomly it changes the order of the default security responses in the generated OpenAPI JSON and YML files. This has various side effects and requires manual reviews in our processes.

Cause: the function io.quarkus.smallrye.openapi.deployment.filter.AutoRolesAllowedFilter#getSecurityResponses uses currently an unsorted hash map to add the 401 and 403 response.

We fixed it for now in our local env by deploying a SNAPSHOT that uses a LinkedHashMap to add the responses.
Its tested and running well already for some builds and we would like to see the stabilization for the export in one of the next LTS bugfixes.

Thanks in advance.

PS: references to the earlier discussion in the SmallRye OpenAPI project

smallrye/smallrye-open-api#1802
smallrye/smallrye-open-api#1803

Implementation ideas

using a LinkedHashMap

[quarkus-bot]

/cc @EricWittmann (openapi), @MikeEdgar (openapi), @phillip-kruger (openapi), @sberyozkin (security)