Upgrade individual bindings

[jonaslagoni]

Should be possible to migrate/upgrade bindings individually without having to convert the entire document.

[ItshMoh]

hello @jonaslagoni are you talking about this individual binding where on method of post is converted into async api format. Not the entire document. Am i going in the right path. Here the async version in 2.0.0 it should be the latest.
OPENAPI

openapi: 3.0.0
info:
  title: Order Service
  version: '1.0'
paths:
  /order/{id}:
    get:
      summary: Retrieve an order by ID
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Order'

  /order:
    post:
      summary: Create a new order
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/Order'
      responses:
        '201':
          description: Order created successfully
components:
  schemas:
    Order:
      type: object
      properties:
        id:
          type: string
        item:
          type: string
        quantity:
          type: integer

`
**ASYNCAPI**
`asyncapi: '2.0.0'
info:
  title: Order Service
  version: '1.0'
channels:
  order/created:
    description: Channel where new orders are published
    publish:
      operationId: publishOrderCreated
      summary: Publish a message when a new order is created
      message:
        contentType: application/json
        payload:
          $ref: '#/components/schemas/Order'
components:
  schemas:
    Order:
      type: object
      properties:
        id:
          type: string
        item:
          type: string
        quantity:
          type: integer
`

[jonaslagoni]

@ItshMoh please format code snippets, no one can read that 😄

But regardless, no I am not talking about OpenAPI at all, only the AsyncAPI bindings, so when a binding changes version from 1.0.0 to 2.0.0, the converter should have the functionality to upgrade the existing AsyncAPI document to use the new bindings.

[ItshMoh]

@jonaslagoni my bad for not formatting the code. Thanks for the clarification.

[ItshMoh]

@jonaslagoni . As i have understood the problem, we should have the flexibility of changing version of one binding
without changing the whole document. For example we just want to change the version of message binding leaving the document.
Am i going in the right path. If you can give more insights to the issue it will be helpful

[ItshMoh]

so like in this http bindings, the user should be able to change the current version ?

cc @jonaslagoni

[jonaslagoni]

@ItshMoh kinda yes, so when binding codeowners make breaking changes, the converter should be able to offer the options for users to migrate bindings as well 😊

[ItshMoh]

what should be the possible approach that i should work upon.?

cc @jonaslagoni

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️