# Source: https://docs.fireworks.ai/tools-sdks/firectl/commands/update-deployed-model.md

# Source: https://docs.fireworks.ai/api-reference/update-deployed-model.md

# Source: https://docs.fireworks.ai/tools-sdks/firectl/commands/update-deployed-model.md

# Source: https://docs.fireworks.ai/api-reference/update-deployed-model.md

# Source: https://docs.fireworks.ai/tools-sdks/firectl/commands/update-deployed-model.md

# Source: https://docs.fireworks.ai/api-reference/update-deployed-model.md

# Update LoRA

## OpenAPI

````yaml patch /v1/accounts/{account_id}/deployedModels/{deployed_model_id}
paths:
  path: /v1/accounts/{account_id}/deployedModels/{deployed_model_id}
  method: patch
  servers:
    - url: https://api.fireworks.ai
  request:
    security:
      - title: BearerAuth
        parameters:
          query: {}
          header:
            Authorization:
              type: http
              scheme: bearer
              description: >-
                Bearer authentication using your Fireworks API key. Format:
                Bearer <API_KEY>
          cookie: {}
    parameters:
      path:
        account_id:
          schema:
            - type: string
              required: true
              description: The Account Id
        deployed_model_id:
          schema:
            - type: string
              required: true
              description: The Deployed Model Id
      query: {}
      header: {}
      cookie: {}
    body:
      application/json:
        schemaArray:
          - type: object
            properties:
              displayName:
                allOf:
                  - type: string
              description:
                allOf:
                  - type: string
                    description: Description of the resource.
              model:
                allOf:
                  - type: string
                    title: |-
                      The resource name of the model to be deployed.
                      e.g. accounts/my-account/models/my-model
              deployment:
                allOf:
                  - type: string
                    description: >-
                      The resource name of the base deployment the model is
                      deployed to.
              default:
                allOf:
                  - type: boolean
                    description: >-
                      If true, this is the default target when querying this
                      model without

                      the `#<deployment>` suffix.

                      The first deployment a model is deployed to will have this
                      field set to true.
              state:
                allOf:
                  - $ref: '#/components/schemas/gatewayDeployedModelState'
                    description: The state of the deployed model.
                    readOnly: true
              serverless:
                allOf:
                  - type: boolean
                    title: True if the underlying deployment is managed by Fireworks
              status:
                allOf:
                  - $ref: '#/components/schemas/gatewayStatus'
                    description: Contains model deploy/undeploy details.
                    readOnly: true
              public:
                allOf:
                  - type: boolean
                    description: If true, the deployed model will be publicly reachable.
            required: true
            title: >-
              The properties of the deployed model being updated.
              `deployed_model.name` must

              be populated with the updated resource's name.
        examples:
          example:
            value:
              displayName: <string>
              description: <string>
              model: <string>
              deployment: <string>
              default: true
              serverless: true
              public: true
        description: >-
          The properties of the deployed model being updated.
          `deployed_model.name` must

          be populated with the updated resource's name.
  response:
    '200':
      application/json:
        schemaArray:
          - type: object
            properties:
              name:
                allOf:
                  - type: string
                    title: >-
                      The resource name. e.g.
                      accounts/my-account/deployedModels/my-deployed-model
                    readOnly: true
              displayName:
                allOf:
                  - type: string
              description:
                allOf:
                  - type: string
                    description: Description of the resource.
              createTime:
                allOf:
                  - type: string
                    format: date-time
                    description: The creation time of the resource.
                    readOnly: true
              model:
                allOf:
                  - type: string
                    title: |-
                      The resource name of the model to be deployed.
                      e.g. accounts/my-account/models/my-model
              deployment:
                allOf:
                  - type: string
                    description: >-
                      The resource name of the base deployment the model is
                      deployed to.
              default:
                allOf:
                  - type: boolean
                    description: >-
                      If true, this is the default target when querying this
                      model without

                      the `#<deployment>` suffix.

                      The first deployment a model is deployed to will have this
                      field set to true.
              state:
                allOf:
                  - $ref: '#/components/schemas/gatewayDeployedModelState'
                    description: The state of the deployed model.
                    readOnly: true
              serverless:
                allOf:
                  - type: boolean
                    title: True if the underlying deployment is managed by Fireworks
              status:
                allOf:
                  - $ref: '#/components/schemas/gatewayStatus'
                    description: Contains model deploy/undeploy details.
                    readOnly: true
              public:
                allOf:
                  - type: boolean
                    description: If true, the deployed model will be publicly reachable.
              updateTime:
                allOf:
                  - type: string
                    format: date-time
                    description: The update time for the deployed model.
                    readOnly: true
            title: 'Next ID: 20'
            refIdentifier: '#/components/schemas/gatewayDeployedModel'
        examples:
          example:
            value:
              name: <string>
              displayName: <string>
              description: <string>
              createTime: '2023-11-07T05:31:56Z'
              model: <string>
              deployment: <string>
              default: true
              state: STATE_UNSPECIFIED
              serverless: true
              status:
                code: OK
                message: <string>
              public: true
              updateTime: '2023-11-07T05:31:56Z'
        description: A successful response.
  deprecated: false
  type: path
components:
  schemas:
    gatewayCode:
      type: string
      enum:
        - OK
        - CANCELLED
        - UNKNOWN
        - INVALID_ARGUMENT
        - DEADLINE_EXCEEDED
        - NOT_FOUND
        - ALREADY_EXISTS
        - PERMISSION_DENIED
        - UNAUTHENTICATED
        - RESOURCE_EXHAUSTED
        - FAILED_PRECONDITION
        - ABORTED
        - OUT_OF_RANGE
        - UNIMPLEMENTED
        - INTERNAL
        - UNAVAILABLE
        - DATA_LOSS
      default: OK
      description: |-
        - OK: Not an error; returned on success.

        HTTP Mapping: 200 OK
         - CANCELLED: The operation was cancelled, typically by the caller.

        HTTP Mapping: 499 Client Closed Request
         - UNKNOWN: Unknown error.  For example, this error may be returned when
        a `Status` value received from another address space belongs to
        an error space that is not known in this address space.  Also
        errors raised by APIs that do not return enough error information
        may be converted to this error.

        HTTP Mapping: 500 Internal Server Error
         - INVALID_ARGUMENT: The client specified an invalid argument.  Note that this differs
        from `FAILED_PRECONDITION`.  `INVALID_ARGUMENT` indicates arguments
        that are problematic regardless of the state of the system
        (e.g., a malformed file name).

        HTTP Mapping: 400 Bad Request
         - DEADLINE_EXCEEDED: The deadline expired before the operation could complete. For operations
        that change the state of the system, this error may be returned
        even if the operation has completed successfully.  For example, a
        successful response from a server could have been delayed long
        enough for the deadline to expire.

        HTTP Mapping: 504 Gateway Timeout
         - NOT_FOUND: Some requested entity (e.g., file or directory) was not found.

        Note to server developers: if a request is denied for an entire class
        of users, such as gradual feature rollout or undocumented allowlist,
        `NOT_FOUND` may be used. If a request is denied for some users within
        a class of users, such as user-based access control, `PERMISSION_DENIED`
        must be used.

        HTTP Mapping: 404 Not Found
         - ALREADY_EXISTS: The entity that a client attempted to create (e.g., file or directory)
        already exists.

        HTTP Mapping: 409 Conflict
         - PERMISSION_DENIED: The caller does not have permission to execute the specified
        operation. `PERMISSION_DENIED` must not be used for rejections
        caused by exhausting some resource (use `RESOURCE_EXHAUSTED`
        instead for those errors). `PERMISSION_DENIED` must not be
        used if the caller can not be identified (use `UNAUTHENTICATED`
        instead for those errors). This error code does not imply the
        request is valid or the requested entity exists or satisfies
        other pre-conditions.

        HTTP Mapping: 403 Forbidden
         - UNAUTHENTICATED: The request does not have valid authentication credentials for the
        operation.

        HTTP Mapping: 401 Unauthorized
         - RESOURCE_EXHAUSTED: Some resource has been exhausted, perhaps a per-user quota, or
        perhaps the entire file system is out of space.

        HTTP Mapping: 429 Too Many Requests
         - FAILED_PRECONDITION: The operation was rejected because the system is not in a state
        required for the operation's execution.  For example, the directory
        to be deleted is non-empty, an rmdir operation is applied to
        a non-directory, etc.

        Service implementors can use the following guidelines to decide
        between `FAILED_PRECONDITION`, `ABORTED`, and `UNAVAILABLE`:
         (a) Use `UNAVAILABLE` if the client can retry just the failing call.
         (b) Use `ABORTED` if the client should retry at a higher level. For
             example, when a client-specified test-and-set fails, indicating the
             client should restart a read-modify-write sequence.
         (c) Use `FAILED_PRECONDITION` if the client should not retry until
             the system state has been explicitly fixed. For example, if an "rmdir"
             fails because the directory is non-empty, `FAILED_PRECONDITION`
             should be returned since the client should not retry unless
             the files are deleted from the directory.

        HTTP Mapping: 400 Bad Request
         - ABORTED: The operation was aborted, typically due to a concurrency issue such as
        a sequencer check failure or transaction abort.

        See the guidelines above for deciding between `FAILED_PRECONDITION`,
        `ABORTED`, and `UNAVAILABLE`.

        HTTP Mapping: 409 Conflict
         - OUT_OF_RANGE: The operation was attempted past the valid range.  E.g., seeking or
        reading past end-of-file.

        Unlike `INVALID_ARGUMENT`, this error indicates a problem that may
        be fixed if the system state changes. For example, a 32-bit file
        system will generate `INVALID_ARGUMENT` if asked to read at an
        offset that is not in the range [0,2^32-1], but it will generate
        `OUT_OF_RANGE` if asked to read from an offset past the current
        file size.

        There is a fair bit of overlap between `FAILED_PRECONDITION` and
        `OUT_OF_RANGE`.  We recommend using `OUT_OF_RANGE` (the more specific
        error) when it applies so that callers who are iterating through
        a space can easily look for an `OUT_OF_RANGE` error to detect when
        they are done.

        HTTP Mapping: 400 Bad Request
         - UNIMPLEMENTED: The operation is not implemented or is not supported/enabled in this
        service.

        HTTP Mapping: 501 Not Implemented
         - INTERNAL: Internal errors.  This means that some invariants expected by the
        underlying system have been broken.  This error code is reserved
        for serious errors.

        HTTP Mapping: 500 Internal Server Error
         - UNAVAILABLE: The service is currently unavailable.  This is most likely a
        transient condition, which can be corrected by retrying with
        a backoff. Note that it is not always safe to retry
        non-idempotent operations.

        See the guidelines above for deciding between `FAILED_PRECONDITION`,
        `ABORTED`, and `UNAVAILABLE`.

        HTTP Mapping: 503 Service Unavailable
         - DATA_LOSS: Unrecoverable data loss or corruption.

        HTTP Mapping: 500 Internal Server Error
      title: >-
        Mimics
        [https://github.com/googleapis/googleapis/blob/master/google/rpc/code.proto]
    gatewayDeployedModelState:
      type: string
      enum:
        - STATE_UNSPECIFIED
        - UNDEPLOYING
        - DEPLOYING
        - DEPLOYED
        - UPDATING
      default: STATE_UNSPECIFIED
      description: |-
        - UNDEPLOYING: The model is being undeployed.
         - DEPLOYING: The model is being deployed.
         - DEPLOYED: The model is deployed and ready for inference.
         - UPDATING: there are updates happening with the deployed model
      title: 'Next ID: 6'
    gatewayStatus:
      type: object
      properties:
        code:
          $ref: '#/components/schemas/gatewayCode'
          description: The status code.
        message:
          type: string
          description: A developer-facing error message in English.
      title: >-
        Mimics
        [https://github.com/googleapis/googleapis/blob/master/google/rpc/status.proto]

````