OpenAPI still exposes@EndpointDisabled endpoints

[gastaldi]

Describe the bug

Having an endpoint like:

@ApplicationScoped
@Path("/client")
@Tag(name = "Client", description = "Client related services")
@EndpointDisabled(name = "quarkus.registry.expose.client.config.yaml", stringValue = "false", disableIfMissing = true)
public class ClientConfigYamlEndpoint {

     @GET
    @Path("/config.yaml")
    @Produces(YAMLMediaTypes.APPLICATION_JACKSON_YAML)
    @Operation(summary = "Example Quarkus Registry Client configuration file")
    public RegistriesConfig clientConfigYaml() {}
}

When browsing the OpenAPI schema using /q/swagger-ui, I can still see the endpoint when the quarkus.registry.expose.client.config.yaml property is missing

Expected behavior

Endpoint is not listed in the OpenAPI schema

Actual behavior

Endpoint is listed and returns 404 when invoked

How to Reproduce?

1. Run mvn quarkus:dev with Expose an example config.yaml over the registry's REST api registry.quarkus.io#197
2. Navigate to http://localhost:8080/q/swagger-ui/
3. The endpoint is listed there, invoking it gives 404

Output of uname -a or ver

macOS m1

Output of java -version

JDK 17

GraalVM version (if different from Java)

22.3.1

Quarkus version or git rev

3.1.2.Final

Build tool (ie. output of mvnw --version or gradlew --version)

Apache Maven 3.9.2

Additional information

Extensions used:

• io.quarkus:quarkus-resteasy-reactive-jackson
• io.quarkus:quarkus-smallrye-openapi

[quarkus-bot]

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

[MikeEdgar]

Looks like a duplicate of #34030

[gastaldi]

Ah crap, I should have searched it better. Thanks @MikeEdgar

[gastaldi]

Duplicate of #34030