Skip to content

Auto generated Actuator endpoints has strange operationId fields #1264

Closed
@bfrggit

Description

@bfrggit

Please note the links_0, handle_1, and handle_2 in the below examples.

I see it is probably related to #88 (comment). If we cannot fix this, can we at least remove these?

  /actuator:
    get:
      tags:
      - Actuator
      summary: Actuator root web endpoint
      operationId: links_0
      responses:
        "200":
          description: OK
          content:
            '*/*':
              schema:
                type: object
                additionalProperties:
                  type: object
                  additionalProperties:
                    $ref: '#/components/schemas/Link'
  /actuator/health:
    get:
      tags:
      - Actuator
      summary: Actuator web endpoint 'health'
      operationId: handle_1
        "200":
          description: OK
          content:
            '*/*':
              schema:
                type: object
  /actuator/health/**:
    get:
      tags:
      - Actuator
      summary: Actuator web endpoint 'health-path'
      operationId: handle_2
      responses:
        "200":
          description: OK
          content:
            '*/*':
              schema:
                type: object

Metadata

Metadata

Assignees

No one assigned

    Labels

    duplicateThis issue or pull request already exists

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions