Skip to content

Allocation Assignment API does NOT support ip & port fields. #14

@torisetxd

Description

@torisetxd

📖 Documentation Improvement

📍 Location

Please specify which part of the documentation needs improvement:

🔍 Current Content

Describes using ip & port as possible fields.
Non existent & inaccurate errors.

✨ Proposed Content & 💡 Suggested Improvement

Simply removing these fields from the table.
Replacing 400 status code:

  • DisplayException (instead of TooManyAllocationsException)
  • Message with: "Cannot assign additional allocations to this server: limit has been reached."

Replacing 503 status code:

  • NoAutoAllocationSpaceAvailableException (instead of NoAvailableAllocationsException)
  • Message with:""Cannot assign additional allocation: no more space available on node."

Removing 409 (AllocationNotAvailableException), it does not exist.

🎁 Additional Value

As a actual working version (although application instead of client), you can use:
PATCH /api/application/servers/{server:id}/build
With either add_allocations or remove_allocations as an array of allocation ids.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions