Using mp.openapi.scan.disable=true on subsequent deployment causes OpenAPI generation issues -------------------------------------------------------------------------------------------- Key: WFWIP-289 URL: https://issues.redhat.com/browse/WFWIP-289 Project: WildFly WIP Issue Type: Bug Components: MP OpenAPI Reporter: Fabio Burzigotti Assignee: Paul Ferraro Priority: Blocker Complex scenario with 4 subsequent deployments. The last one adds the `mp.openapi.scan.disable=true` MP Config core property - consequently no `mp.openapi.extensions.path` MP Config vendor extension property is defined. This causes the server to behave in non-deterministic way for generation of OpenAPI document at standard `/openapi` URL. "Non-deterministic" means that - when the test is executed several times - the generated document contains elements either from first or second deployments (third one is not registering the endpoint and is skipped as expected).