fix template format

fix template format

remote: Support for password authentication was removed on August 13, 2021.
remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
fatal: Authentication failed for 'https://github.com/Jumpscale/jscockpit.git/'


fix(apidoc): Remove OrganizationView and JoinOrganizationInvitationView from raml (#571)

Use Organization and JoinOrganizationInvitation instead since they are the same objects
Also remove MemberView that is no longer returned by the api

Closes #569

fatal: unable to access 'https://github.com/itsyouonline/identityserver.git/': The requested URL returned error: 403


Initial contract api definition

Initial contract api definition

#%RAML 1.0
title: ItsYouOnline
version: 0.1
baseUri: /

types:
  Signature:
    properties:
      signedBy: string
      date: date
      signature: string

  Contract:
    properties:
      parties:
        type: string[]
        minItems: 2
        uniqueItems: true
      content: string
      contractType: string
      expires: date
      contractId:
        type: string
        description: |
          The contractId is the hash of the parties, the content, the contractType and the expiration date.
          To calculate the hash, take the json representation of the contract without the id and signatures, trim the newlines or spaces (except when they appear in the values) and encode in  utf8.
          From this result, take a SHA256 followed by a RIPEMD160, next base58CheckEncode the result with a 0x00 prefix.

      signatures: Signature[]

/contracts:
  post:
    description: Create a new contract.
    responses:
      201:
        body:
          application/json:
            type: Contract
      401:
        description: Unauthorized

  /{contractId}:
    get:
      description: Get a contract
      responses:
        200:
          body:
            application/json:
              type: Contract
        404:
          description: Not found
  /{contractId}/signatures:
    post:
        description: Sign a contract
        body:
          application/json:
            type: Signature

error: pathspec 'specifications/api/contracts.raml' did not match any file(s) known to git


update return code for update blueprint call


Add petstore.raml file in 0.8 format

Add petstore.raml file in 0.8 format

#%RAML 0.8
title: Swagger Petstore
version: 1.0.0
documentation:
- title: Swagger Petstore
  content: |
    This is a sample server Petstore server.

    [Learn about Swagger](http://swagger.io) or join the IRC channel `#swagger` on irc.freenode.net.

    For this sample, you can use the api key `special-key` to test the authorization filters
baseUri: http://petstore.swagger.io/v2
securitySchemes:
- auth:
    type: x-custom
    describedBy:
      headers:
        api_key:
          type: String
          default:
          required: true
          displayName: api_key
schemas:
- Pet: |
    {
      "id": "Pet",
      "title": "Pet",
      "type": "object",
      "properties": {
        "name": {
          "type": "string"
        },
        "photoUrls": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "id": {
          "type": "integer",
          "format": "int64"
        },
        "category": {
          "id": "Category",
          "title": "Category",
          "type": "object",
          "properties": {
            "id": {
              "type": "integer",
              "format": "int64"
            },
            "name": {
              "type": "string"
            }
          }
        },
        "tags": {
          "type": "array",
          "items": {
            "id": "Tag",
            "title": "Tag",
            "type": "object",
            "properties": {
              "id": {
                "type": "integer",
                "format": "int64"
              },
              "name": {
                "type": "string"
              }
            }
          }
        },
        "status": {
          "description": "pet status in the store",
          "type": "string"
        }
      },
      "required": [
        "name",
        "photoUrls"
      ]
    }
- Pet-array: |
    {
      "type": "array",
      "items": {
        "id": "Pet",
        "title": "Pet",
        "type": "object",
        "properties": {
          "name": {
            "type": "string"
          },
          "photoUrls": {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          "id": {
            "type": "integer",
            "format": "int64"
          },
          "category": {
            "id": "Category",
            "title": "Category",
            "type": "object",
            "properties": {
              "id": {
                "type": "integer",
                "format": "int64"
              },
              "name": {
                "type": "string"
              }
            }
          },
          "tags": {
            "type": "array",
            "items": {
              "id": "Tag",
              "title": "Tag",
              "type": "object",
              "properties": {
                "id": {
                  "type": "integer",
                  "format": "int64"
                },
                "name": {
                  "type": "string"
                }
              }
            }
          },
          "status": {
            "description": "pet status in the store",
            "type": "string"
          }
        },
        "required": [
          "name",
          "photoUrls"
        ]
      }
    }
- Order: |
    {
      "id": "Order",
      "title": "Order",
      "type": "object",
      "properties": {
        "id": {
          "type": "integer",
          "format": "int64"
        },
        "petId": {
          "type": "integer",
          "format": "int64"
        },
        "quantity": {
          "type": "integer",
          "format": "int32"
        },
        "shipDate": {
          "type": "string",
          "format": "date-time"
        },
        "status": {
          "description": "Order Status",
          "type": "string"
        },
        "complete": {
          "type": "boolean"
        }
      }
    }
- User: |
    {
      "id": "User",
      "title": "User",
      "type": "object",
      "properties": {
        "id": {
          "type": "integer",
          "format": "int64"
        },
        "username": {
          "type": "string"
        },
        "firstName": {
          "type": "string"
        },
        "lastName": {
          "type": "string"
        },
        "email": {
          "type": "string"
        },
        "password": {
          "type": "string"
        },
        "phone": {
          "type": "string"
        },
        "userStatus": {
          "description": "User Status",
          "type": "integer",
          "format": "int32"
        }
      }
    }
- User-array: |
    {
      "type": "array",
      "items": {
        "id": "User",
        "title": "User",
        "type": "object",
        "properties": {
          "id": {
            "type": "integer",
            "format": "int64"
          },
          "username": {
            "type": "string"
          },
          "firstName": {
            "type": "string"
          },
          "lastName": {
            "type": "string"
          },
          "email": {
            "type": "string"
          },
          "password": {
            "type": "string"
          },
          "phone": {
            "type": "string"
          },
          "userStatus": {
            "description": "User Status",
            "type": "integer",
            "format": "int32"
          }
        }
      }
    }
/pets:
  /findByStatus:
    get:
      securedBy:
      - auth
      displayName: findPetsByStatus
      description: Finds Pets by status
      responses:
        200:
          description: successful operation
          body:
            application/json:
              schema: Pet-array
        400:
          description: Invalid status value
      queryParameters:
        status:
          description: Status values that need to be considered for filter
          type: string
          required: false
          displayName: status
  /findByTags:
    get:
      securedBy:
      - auth
      displayName: findPetsByTags
      description: Finds Pets by tags
      responses:
        200:
          description: successful operation
          body:
            application/json:
              schema: Pet-array
        400:
          description: Invalid tag value
      queryParameters:
        tags:
          description: Tags to filter by
          type: string
          required: false
          displayName: tags
  /{petId}:
    uriParameters:
      petId:
        description: ID of pet that needs to be fetched
        type: integer
        required: true
        displayName: petId
    get:
      securedBy:
      - auth
      displayName: getPetById
      description: Find pet by ID
      responses:
        200:
          description: successful operation
          body:
            application/json:
              schema: Pet
        404:
          description: Pet not found
        400:
          description: Invalid ID supplied
    post:
      securedBy:
      - auth
      displayName: updatePetWithForm
      description: Updates a pet in the store with form data
      responses:
        405:
          description: Invalid input
    delete:
      securedBy:
      - auth
      displayName: deletePet
      description: Deletes a pet
      responses:
        400:
          description: Invalid pet value
      headers:
        api_key:
          description:
          type: string
          required: true
          displayName: api_key
  put:
    securedBy:
    - auth
    body:
      application/json:
        schema: Pet
    displayName: updatePet
    description: Update an existing pet
    responses:
      405:
        description: Validation exception
      404:
        description: Pet not found
      400:
        description: Invalid ID supplied
  post:
    securedBy:
    - auth
    body:
      application/json:
        schema: Pet
    displayName: addPet
    description: Add a new pet to the store
    responses:
      405:
        description: Invalid input
/stores/order:
  /{orderId}:
    uriParameters:
      orderId:
        description: ID of pet that needs to be fetched
        type: string
        required: true
        displayName: orderId
    get:
      securedBy:
      - auth
      displayName: getOrderById
      description: Find purchase order by ID
      responses:
        200:
          description: successful operation
          body:
            application/json:
              schema: Order
        404:
          description: Order not found
        400:
          description: Invalid ID supplied
    delete:
      securedBy:
      - auth
      displayName: deleteOrder
      description: Delete purchase order by ID
      responses:
        404:
          description: Order not found
        400:
          description: Invalid ID supplied
  post:
    securedBy:
    - auth
    body:
      application/json:
        schema: Order
    displayName: placeOrder
    description: Place an order for a pet
    responses:
      200:
        description: successful operation
        body:
          application/json:
            schema: Order
      400:
        description: Invalid Order
/users:
  /createWithArray:
    post:
      securedBy:
      - auth
      body:
        application/json:
          schema: User-array
      displayName: createUsersWithArrayInput
      description: Creates list of users with given input array
      responses:
        500:
          description: successful operation
  /createWithList:
    post:
      securedBy:
      - auth
      body:
        application/json:
          schema: User-array
      displayName: createUsersWithListInput
      description: Creates list of users with given input array
      responses:
        500:
          description: successful operation
  /login:
    get:
      securedBy:
      - auth
      displayName: loginUser
      description: Logs user into the system
      responses:
        200:
          description: successful operation
        400:
          description: Invalid username/password supplied
      queryParameters:
        username:
          description: The user name for login
          type: string
          required: false
          displayName: username
        password:
          description: The password for login in clear text
          type: string
          required: false
          displayName: password
  /logout:
    get:
      securedBy:
      - auth
      displayName: logoutUser
      description: Logs out current logged in user session
      responses:
        500:
          description: successful operation
  /{username}:
    uriParameters:
      username:
        description: The name that needs to be fetched. Use user1 for testing.
        type: string
        required: true
        displayName: username
    get:
      securedBy:
      - auth
      displayName: getUserByName
      description: Get user by user name
      responses:
        200:
          description: successful operation
          body:
            application/json:
              schema: User
        404:
          description: User not found
        400:
          description: Invalid username supplied
    put:
      securedBy:
      - auth
      body:
        application/json:
          schema: User
      displayName: updateUser
      description: Updated user
      responses:
        404:
          description: User not found
        400:
          description: Invalid user supplied
    delete:
      securedBy:
      - auth
      displayName: deleteUser
      description: Delete user
      responses:
        404:
          description: User not found
        400:
          description: Invalid username supplied
  post:
    securedBy:
    - auth
    body:
      application/json:
        schema: User
    displayName: createUser
    description: Create user
    responses:
      500:
        description: successful operation

error: pathspec 'petstore.raml' did not match any file(s) known to git


Change the description of the PUT method semantics (#6269)

Summary: misleading sentence about all apps being upgraded was changed.

JIRA issues: MARATHON-3104

###
  # Get a list of applications
  #
  get:
    description:
      Get the list of running applications. Several filters can be applied via the following query parameters.
    is: [ secured ]
    queryParameters:
      cmd:
        required: false
        description: Filter the result to only return apps whose `cmd` field contains the given value
        example: java
      id:
        required: false
        description: Filter the result to only return apps whose `id` is or contains the given value
        example: /us-east/database/memsql
      label:
        required: false
        description:
          A label selector query contains one or more label selectors, which are comma separated.
          Marathon supports three types of selectors existence-based, equality-based and set-based.
          In the case of multiple selectors, all must be satisfied so comma separator acts as an AND logical operator.
          Labels and values must consist of alphanumeric characters plus `-` `_` and `.` `-A-Za-z0-9_.`.
          Any other character is possible, but must be escaped with a backslash character.

          * Existence based Selector Query Matches the existence of a label

            Example: my_label,environment

          * Equality based Selector Query Matches existence of labels and the (non) equality of the value.

            Example: environment==production, tier!=frontend

          * Set based Selector Query Matches existence of labels and the (non) existence of the value in a given set

            Example: environment in (stage,production), tier notin (frontend, service)

        example: my_label, environment==production, tier!=frontend\ tier, deployed in (us, eu), deployed notin (aa, bb)
      embed:
        required: false
        description:
          Embeds nested resources that match the supplied path.
          You can specify this parameter multiple times with different values.

          - apps.tasks embed all tasks of each application

          Note: if this embed is definded, it automatically sets apps.deployments but this will change in a future release.
          Please define all embeds explicitly.

          - apps.counts embed all task counts (tasksStaged, tasksRunning, tasksHealthy, tasksUnhealthy)

          Note: currently embedded by default but this will change in a future release.
          Please define all embeds explicitly.

          - apps.deployments embed all deployment identifier, if the related app currently is in deployment.

          - apps.readiness embed all readiness check results

          - apps.lastTaskFailure embeds the lastTaskFailure for the application if there is one.

          - apps.failures Shorthand for apps.lastTaskFailure, apps.tasks, apps.counts and apps.deployments.

          Note: deprecated and will be removed in future versions
          Please define all embeds explicitly.

          - apps.taskStats exposes task statistics in the JSON.

        enum: [ apps.tasks, apps.count, apps.deployments, apps.lastTaskFailure, apps.failures, apps.taskStats ]
        example: apps.tasks
    responses:
      200:
        description: "The list of applications that match the defined filters"
        body:
          application/json:
            example: !include examples/app_list.json

  ###
  # update a list of applications
  #
  put:
    description:
      Change multiple applications either by upgrading existing ones or creating new ones.
      If there is an update to an already running application, the application gets upgraded.
      Instances of this application will be started or restarted
      according to the usual logic to meet the requirements of the new definition. Usually, restart is required
      if the application configuration has changed. Restart is not necessary for scaling-only changes.
      The order of dependencies will be applied correctly.
      The upgradeStrategy defines the behaviour of the upgrade.

      If the id of the application is not known, the application gets started.
      The order of dependencies will be applied correctly.
      It is possible to mix upgrades and installs.

      If you have more complex scenarios with upgrades, use the groups endpoint.

      Note:  This operation will create a deployment. The operation finishes, if the deployment succeeds.
       You can query the deployments endoint to see the status of the deployment.
    is: [ secured, deployable ]
    queryParameters:
      partialUpdate:
        required: false
        default: "true"
        description: |
          Without specifying this parameter, this method has a patch like semantic:
          All values that are not defined in the json, will not change existing values.
          This was the default behaviour in previous Marathon versions.
          For backward compatibility, we will not change this behaviour, but let users opt in for a proper PUT.
          Note: We will change the default behaviour in the next Marathon version to support PATCH and PUT as HTTP methods.
    body:
      application/json:
        example: !include examples/apps_create.json
        type: app.App[]
    responses:
      409:
        description: There is an already deployed application with this name
        body:
          application/json:
            type: error.Error
            example: |
              {"message":"An app with id [/existing_app] already exists."}
      400:
        description: The application definition provided in the body is not valid.
        body:
          application/json:
            type: error.Error
            example: |
               {"message":"Invalid JSON","details":[{"path":"/id","errors":["error.expected.jsstring"]}]}
      422:
        description: The entity send can not be preocessed, since there are validation errors
        body:
          application/json:
            type: error.Error
            example: |
                {
                  "message": "Object is not valid",
                  "details": [
                    {
                      "path": "/upgradeStrategy/minimumHealthCapacity",
                      "errors": [
                        "is greater than 1"
                      ]
                    }
                  ]
                }

  ###
  # apply a patch update to a list of applications
  #
  patch:
    description:
      Change multiple existing applications by applying a patch.
      Instances of these applications will be started or restarted according to the ususal logic to meet the
      requirements of the new app definitions. Usually, restart is required if the application configuration was changed
      (except for scaling changes).
      The order of dependencies will be applied correctly.
      Each upgradeStrategy defines the behaviour of the upgrade for the related app.

      The whole operation fails if the IDs of one or more applications are unknown.
      The order of dependencies will be applied correctly.

      If you have more complex scenarios with upgrades, use the groups endpoint.

      Note:  This operation will create a deployment. The operation finishes, if the deployment succeeds.
       You can query the deployments endoint to see the status of the deployment.
    is: [ secured, deployable ]
    queryParameters:
    body:
      application/json:
        example: !include examples/apps_patch.json
        type: app.App[]
    responses:
      409:
        description: One or more specified applications is currently locked by a deployment
        body:
          application/json:
            type: error.Error
            example: |
              {"message":"App is locked by one or more deployments."}
      400:
        description: The application definition provided in the body is not valid.
        body:
          application/json:
            type: error.Error
            example: |
               {"message":"Invalid JSON","details":[{"path":"/id","errors":["error.expected.jsstring"]}]}
      422:
        description: The entity send can not be processed, since there are validation errors
        body:
          application/json:
            type: error.Error
            example: |
                {
                  "message": "Object is not valid",
                  "details": [
                    {
                      "path": "/upgradeStrategy/minimumHealthCapacity",
                      "errors": [
                        "is greater than 1"
                      ]
                    }
                  ]
                }

  ###
  # Create application
  #
  post:
    description:
      Create and start a new application.

      Note:  This operation will create a deployment. The operation finishes, if the deployment succeeds.
       You can query the deployments endoint to see the status of the deployment.
    is: [ secured, deployable ]
    body:
      application/json:
        example: !include examples/app.json
        type: app.App
    responses:
      201:
        description: The application has been created and a deployment is started.
        body:
          application/json:
            example: !include examples/app.json
      409:
        description: There is an already deployed application with this name
        body:
          application/json:
            type: error.Error
            example: |
              {"message":"An app with id [/existing_app] already exists."}
      400:
        description: The application definition provided in the body is not valid.
        body:
          application/json:
            type: error.Error
            example: |
                {"message":"Invalid JSON","details":[{"path":"/id","errors":["error.expected.jsstring"]}]}
      422:
        description: The entity send can not be preocessed, since there are validation errors
        body:
          application/json:
            type: error.Error
            example: |
                {
                "message": "Object is not valid",
                "details": [
                  {
                    "path": "/upgradeStrategy/minimumHealthCapacity",
                    "errors": [
                      "is greater than 1"
                    ]
                  }
                ]
                }

  /{app_id}:

    ###
    # Get a specific app
    #
    get:
      description:
        Get the application with id `app_id`.
        The response includes some status information besides the current configuration of the app.
        You can specify optional embed arguments, to get more embedded information.
      is: [ secured ]
      queryParameters:
        embed:
          description:
            Embeds nested resources that match the supplied path.
            You can specify this parameter multiple times with different values.

            - app.tasks. embed tasks
            Note: if this embed is definded, it automatically sets apps.deployments but this will change in a future release.
            Please define all embeds explicitly.

            - app.counts. embed all task counts (tasksStaged, tasksRunning, tasksHealthy, tasksUnhealthy)

            Note: currently embedded by default but this will change in a future release.
            Please define all embeds explicitly.

            - app.deployments. embed all deployment identifier, if the related app currently is in deployment.

            - app.readiness embed all readiness check results

            - app.lastTaskFailure embeds the lastTaskFailure for the application if there is one.

            - app.failures Shorthand for apps.lastTaskFailure, apps.tasks, apps.counts and apps.deployments.

            Note: deprecated and will be removed in future versions
            Please define all embeds explicitly.

            - app.taskStats exposes task statistics in the JSON.

          enum: [ app.tasks, app.count, app.deployments, app.lastTaskFailure, app.failures, app.taskStats ]
          #example: embed=app.deployments&embed=app.lastTaskFailure
      responses:
        200:
          body:
            application/json:
              #type: app.AppList
              example: !include examples/app_list.json
        404:
          description: No app found with this `app_id`.
          body:
            application/json:
              type: error.Error
              example: |
                { "message": "App '/not_existent' does not exist" }

    ###
    # Update a specific app
    #
    put:
      description:
        Replaces parameters of a running application. If no application with the given id
        exists, it will be created. If there is an application with this id, all running instances get
        upgraded to the new definition.

        Note:  This operation will create a deployment. The operation finishes, if the deployment succeeds.
         You can query the deployments endoint to see the status of the deployment.
      is: [ secured, deployable ]
      queryParameters:
        partialUpdate:
          required: false
          default: "true"
          description: |
            Without specifying this parameter, this method has a patch like semantic:
            All values that are not defined in the json, will not change existing values.
            This was the default behaviour in previous Marathon versions.
            For backward compatibility, we will not change this behaviour, but let users opt in for a proper PUT.
            Note: We will change the default behaviour in the next Marathon version to support PATCH and PUT as HTTP methods.
      body:
        application/json:
          example: !include examples/app.json
          type: app.App
      responses:
        201:
          description: The application has been created and a deployment is started.
          body:
            application/json:
              type: deploymentResult.DeploymentResult
              example: !include examples/deployments_result.json
        404:
          description: No task found with this `app_id`.
          body:
            application/json:
              type: error.Error
              example: |
                  { "message": "App '/not_existent' does not exist" }
        400:
          description: The application definition provided in the body is not valid.
          body:
            application/json:
              type: error.Error
              example: |
                {"message":"Invalid JSON","details":[{"path":"/id","errors":["error.expected.jsstring"]}]}
        422:
          description: The entity sent can not be preocessed, since there are validation errors
          body:
            application/json:
              type: error.Error
              example: |
                {
                  "message": "Object is not valid",
                  "details": [
                    {
                      "path": "/upgradeStrategy/minimumHealthCapacity",
                      "errors": [
                        "is greater than 1"
                      ]
                   }
                  ]
                }

    ###
    # Apply a patch update to a specific app.
    #
    patch:
      description:
        Replaces parameters of a running application. Instances of this application will be started or restarted
        according to the usual logic to meet the requirements of the new definition. Usually, restart is required
        if the application configuration was changed (except for scaling changes).
        Any given application ID will be ignored.

        Note:  This operation will create a deployment. The operation finishes, if the deployment succeeds.
         You can query the deployments endoint to see the status of the deployment.
      is: [ secured, deployable ]
      queryParameters:
      body:
        application/json:
          example: !include examples/app_patch.json
          type: app.App
      responses:
        200:
          description: The application has been updated and a deployment is started.
          body:
            application/json:
              type: deploymentResult.DeploymentResult
              example: !include examples/deployments_result.json
        404:
          description: No task found with this `app_id`.
          body:
            application/json:
              type: error.Error
              example: |
                  { "message": "App '/not_existent' does not exist" }
        400:
          description: The application definition provided in the body is not valid.
          body:
            application/json:
              type: error.Error
              example: |
                {"message":"Invalid JSON","details":[{"path":"/id","errors":["error.expected.jsstring"]}]}
        422:
          description: The entity sent can not be preocessed, since there are validation errors
          body:
            application/json:
              type: error.Error
              example: |
                {
                  "message": "Object is not valid",
                  "details": [
                    {
                      "path": "/upgradeStrategy/minimumHealthCapacity",
                      "errors": [
                        "is greater than 1"
                      ]
                   }
                  ]
                }

    ###
    # Delete a specific app
    #
    delete:
      description: Destroy an application. All data about that application will be deleted.

        Note:  This operation will create a deployment. The operation finishes, if the deployment succeeds.
        You can query the deployments endoint to see the status of the deployment.
      is: [ secured, deployable ]
      responses:
        404:
          description: No app with this id known.
          body:
            application/json:
              type: error.Error
              example: |
                {"message":"App '/not-existing' does not exist"}

    /restart:
      ###
      # Restart this application
      #
      post:
        description: Restart all tasks of this application.
        is: [ secured, deployable ]
        responses:
          404:
            description: No task found with this `app_id`.
            body:
              application/json:
                type: error.Error
                example: |
                  { "message": "App '/not_existent' does not exist" }

    /tasks:
      ###
      # Get all tasks of an application
      #
      get:
        description: List all running tasks for application `app_id`.
        is: [ secured ]
        responses:
          200:
            description: The list of running tasks for application `app_id`.
            body:
              application/json:
                type: task.TaskList
                example: !include examples/app_tasks.json
              text/plain:
                example: |
                    minecraft_survival-world 10013 srv7.hw.ca1.mesosphere.com:31756
          404:
            description: No task found with this `app_id`.
            body:
              application/json:
                example: |
                  { "message": "App '/not_existent' does not exist" }

      ###
      # Kill tasks of an application
      #
      delete:
        description: Kill tasks that belong to the application `app_id`
        is: [ secured, deployable ]
        queryParameters:
          host:
            description: all tasks of that application on the supplied slave are killed
          scale:
            description: If `scale=true` is specified, then the application is scaled down by the number of killed tasks. Only possible if `wipe=false` or not specified.
            default: "false"
          wipe:
            description: If `wipe=true` is specified and the app uses local persistent volumes, associated dynamic reservations will be unreserved, and persistent volumes will be destroyed. Only possible if `scale=false` or not specified.
            default: "false"
        responses:

          200:
            description: If scale=false, all tasks that were killed are returned.
              If scale=true, than a deployment is triggered and the deployment is returned.
            body:
              application/json:
                type: task.TaskList | deploymentResult.DeploymentResult
                example: !include examples/app_tasks.json
          404:
            description: No task found with this `app_id`.
            body:
              application/json:
                example: |
                  { "message": "App '/not_existent' does not exist" }

      /{task_id}:
        ###
        # Delete a single task
        #
        delete:
          description: Kill the task with ID `task_id` that belongs to the application `app_id`.
          is: [ secured, deployable ]
          queryParameters:
            scale:
              description: If `scale=true` is specified, then the application is scaled down by the number of killed tasks. Only possible if `wipe=false` or not specified.
              default: "false"
            wipe:
              description: If `wipe=true` is specified and the app uses local persistent volumes, associated dynamic reservations will be unreserved, and persistent volumes will be destroyed. Only possible if `scale=false` or not specified.
              default: "false"
          responses:
            200:
              description: If scale=false, the task that was killed is returned.
                If scale=true, than a deployment is triggered and the deployment is returned.
              body:
                application/json:
                  type: task.TaskSingle | deploymentResult.DeploymentResult
                  example: !include examples/app_task.json
            404:
              description: No task found with this task_id.
              body:
                application/json:
                  type: error.Error
                  example: |
                    {"message":"Task 'not-existing' does not exist"}

    ###
    # List versions
    #
    /versions:
      get:
        description: List the versions of the application with id `app_id`
        is: [ secured ]
        responses:
          200:
            description: The list of versions of the application
            body:
              application/json:
                example: |
                  { "versions": [ "2014-03-01T23:42:20.938Z" ] }
          404:
            description: No task found with this `app_id`.
            body:
              application/json:
                type: error.Error
                example: |
                  { "message": "App '/not_existent' does not exist" }

      /{version}:
        get:
          description: List the configuration of the application with id `app_id` at version `version`.
          is: [ secured ]
          responses:
            200:
              description: The application definition at that point in time.
              body:
                application/json:
                  type: app.App
                  example: !include examples/app.json
            404:
              description: No task found with this `app_id`.
              body:
                application/json:
                  example: |
                    { "message": "App '/not_existent' does not exist" }

###
  # Get a list of applications
  #
  get:
    description:
      Get the list of running applications. Several filters can be applied via the following query parameters.
    is: [ secured ]
    queryParameters:
      cmd:
        required: false
        description: Filter the result to only return apps whose `cmd` field contains the given value
        example: java
      id:
        required: false
        description: Filter the result to only return apps whose `id` is or contains the given value
        example: /us-east/database/memsql
      label:
        required: false
        description:
          A label selector query contains one or more label selectors, which are comma separated.
          Marathon supports three types of selectors existence-based, equality-based and set-based.
          In the case of multiple selectors, all must be satisfied so comma separator acts as an AND logical operator.
          Labels and values must consist of alphanumeric characters plus `-` `_` and `.` `-A-Za-z0-9_.`.
          Any other character is possible, but must be escaped with a backslash character.

          * Existence based Selector Query Matches the existence of a label

            Example: my_label,environment

          * Equality based Selector Query Matches existence of labels and the (non) equality of the value.

            Example: environment==production, tier!=frontend

          * Set based Selector Query Matches existence of labels and the (non) existence of the value in a given set

            Example: environment in (stage,production), tier notin (frontend, service)

        example: my_label, environment==production, tier!=frontend\ tier, deployed in (us, eu), deployed notin (aa, bb)
      embed:
        required: false
        description:
          Embeds nested resources that match the supplied path.
          You can specify this parameter multiple times with different values.

          - apps.tasks embed all tasks of each application

          Note: if this embed is definded, it automatically sets apps.deployments but this will change in a future release.
          Please define all embeds explicitly.

          - apps.counts embed all task counts (tasksStaged, tasksRunning, tasksHealthy, tasksUnhealthy)

          Note: currently embedded by default but this will change in a future release.
          Please define all embeds explicitly.

          - apps.deployments embed all deployment identifier, if the related app currently is in deployment.

          - apps.readiness embed all readiness check results

          - apps.lastTaskFailure embeds the lastTaskFailure for the application if there is one.

          - apps.failures Shorthand for apps.lastTaskFailure, apps.tasks, apps.counts and apps.deployments.

          Note: deprecated and will be removed in future versions
          Please define all embeds explicitly.

          - apps.taskStats exposes task statistics in the JSON.

        enum: [ apps.tasks, apps.count, apps.deployments, apps.lastTaskFailure, apps.failures, apps.taskStats ]
        example: apps.tasks
    responses:
      200:
        description: "The list of applications that match the defined filters"
        body:
          application/json:
            example: !include examples/app_list.json

  ###
  # update a list of applications
  #
  put:
    description:
      Change multiple applications either by upgrading existing ones or creating new ones.
      If there is an update to an already running application, the application gets upgraded.
      All instances of this application get replaced by the new version.
      The order of dependencies will be applied correctly.
      The upgradeStrategy defines the behaviour of the upgrade.

      If the id of the application is not known, the application gets started.
      The order of dependencies will be applied correctly.
      It is possible to mix upgrades and installs.

      If you have more complex scenarios with upgrades, use the groups endpoint.

      Note:  This operation will create a deployment. The operation finishes, if the deployment succeeds.
       You can query the deployments endoint to see the status of the deployment.
    is: [ secured, deployable ]
    queryParameters:
      partialUpdate:
        required: false
        default: "true"
        description: |
          Without specifying this parameter, this method has a patch like semantic:
          All values that are not defined in the json, will not change existing values.
          This was the default behaviour in previous Marathon versions.
          For backward compatibility, we will not change this behaviour, but let users opt in for a proper PUT.
          Note: We will change the default behaviour in the next Marathon version to support PATCH and PUT as HTTP methods.
    body:
      application/json:
        example: !include examples/apps_create.json
        type: app.App[]
    responses:
      409:
        description: There is an already deployed application with this name
        body:
          application/json:
            type: error.Error
            example: |
              {"message":"An app with id [/existing_app] already exists."}
      400:
        description: The application definition provided in the body is not valid.
        body:
          application/json:
            type: error.Error
            example: |
               {"message":"Invalid JSON","details":[{"path":"/id","errors":["error.expected.jsstring"]}]}
      422:
        description: The entity send can not be preocessed, since there are validation errors
        body:
          application/json:
            type: error.Error
            example: |
                {
                  "message": "Object is not valid",
                  "details": [
                    {
                      "path": "/upgradeStrategy/minimumHealthCapacity",
                      "errors": [
                        "is greater than 1"
                      ]
                    }
                  ]
                }

  ###
  # apply a patch update to a list of applications
  #
  patch:
    description:
      Change multiple existing applications by applying a patch.
      Instances of these applications will be started or restarted according to the ususal logic to meet the
      requirements of the new app definitions. Usually, restart is required if the application configuration was changed
      (except for scaling changes).
      The order of dependencies will be applied correctly.
      Each upgradeStrategy defines the behaviour of the upgrade for the related app.

      The whole operation fails if the IDs of one or more applications are unknown.
      The order of dependencies will be applied correctly.

      If you have more complex scenarios with upgrades, use the groups endpoint.

      Note:  This operation will create a deployment. The operation finishes, if the deployment succeeds.
       You can query the deployments endoint to see the status of the deployment.
    is: [ secured, deployable ]
    queryParameters:
    body:
      application/json:
        example: !include examples/apps_patch.json
        type: app.App[]
    responses:
      409:
        description: One or more specified applications is currently locked by a deployment
        body:
          application/json:
            type: error.Error
            example: |
              {"message":"App is locked by one or more deployments."}
      400:
        description: The application definition provided in the body is not valid.
        body:
          application/json:
            type: error.Error
            example: |
               {"message":"Invalid JSON","details":[{"path":"/id","errors":["error.expected.jsstring"]}]}
      422:
        description: The entity send can not be processed, since there are validation errors
        body:
          application/json:
            type: error.Error
            example: |
                {
                  "message": "Object is not valid",
                  "details": [
                    {
                      "path": "/upgradeStrategy/minimumHealthCapacity",
                      "errors": [
                        "is greater than 1"
                      ]
                    }
                  ]
                }

  ###
  # Create application
  #
  post:
    description:
      Create and start a new application.

      Note:  This operation will create a deployment. The operation finishes, if the deployment succeeds.
       You can query the deployments endoint to see the status of the deployment.
    is: [ secured, deployable ]
    body:
      application/json:
        example: !include examples/app.json
        type: app.App
    responses:
      201:
        description: The application has been created and a deployment is started.
        body:
          application/json:
            example: !include examples/app.json
      409:
        description: There is an already deployed application with this name
        body:
          application/json:
            type: error.Error
            example: |
              {"message":"An app with id [/existing_app] already exists."}
      400:
        description: The application definition provided in the body is not valid.
        body:
          application/json:
            type: error.Error
            example: |
                {"message":"Invalid JSON","details":[{"path":"/id","errors":["error.expected.jsstring"]}]}
      422:
        description: The entity send can not be preocessed, since there are validation errors
        body:
          application/json:
            type: error.Error
            example: |
                {
                "message": "Object is not valid",
                "details": [
                  {
                    "path": "/upgradeStrategy/minimumHealthCapacity",
                    "errors": [
                      "is greater than 1"
                    ]
                  }
                ]
                }

  /{app_id}:

    ###
    # Get a specific app
    #
    get:
      description:
        Get the application with id `app_id`.
        The response includes some status information besides the current configuration of the app.
        You can specify optional embed arguments, to get more embedded information.
      is: [ secured ]
      queryParameters:
        embed:
          description:
            Embeds nested resources that match the supplied path.
            You can specify this parameter multiple times with different values.

            - app.tasks. embed tasks
            Note: if this embed is definded, it automatically sets apps.deployments but this will change in a future release.
            Please define all embeds explicitly.

            - app.counts. embed all task counts (tasksStaged, tasksRunning, tasksHealthy, tasksUnhealthy)

            Note: currently embedded by default but this will change in a future release.
            Please define all embeds explicitly.

            - app.deployments. embed all deployment identifier, if the related app currently is in deployment.

            - app.readiness embed all readiness check results

            - app.lastTaskFailure embeds the lastTaskFailure for the application if there is one.

            - app.failures Shorthand for apps.lastTaskFailure, apps.tasks, apps.counts and apps.deployments.

            Note: deprecated and will be removed in future versions
            Please define all embeds explicitly.

            - app.taskStats exposes task statistics in the JSON.

          enum: [ app.tasks, app.count, app.deployments, app.lastTaskFailure, app.failures, app.taskStats ]
          #example: embed=app.deployments&embed=app.lastTaskFailure
      responses:
        200:
          body:
            application/json:
              #type: app.AppList
              example: !include examples/app_list.json
        404:
          description: No app found with this `app_id`.
          body:
            application/json:
              type: error.Error
              example: |
                { "message": "App '/not_existent' does not exist" }

    ###
    # Update a specific app
    #
    put:
      description:
        Replaces parameters of a running application. If no application with the given id
        exists, it will be created. If there is an application with this id, all running instances get
        upgraded to the new definition.

        Note:  This operation will create a deployment. The operation finishes, if the deployment succeeds.
         You can query the deployments endoint to see the status of the deployment.
      is: [ secured, deployable ]
      queryParameters:
        partialUpdate:
          required: false
          default: "true"
          description: |
            Without specifying this parameter, this method has a patch like semantic:
            All values that are not defined in the json, will not change existing values.
            This was the default behaviour in previous Marathon versions.
            For backward compatibility, we will not change this behaviour, but let users opt in for a proper PUT.
            Note: We will change the default behaviour in the next Marathon version to support PATCH and PUT as HTTP methods.
      body:
        application/json:
          example: !include examples/app.json
          type: app.App
      responses:
        201:
          description: The application has been created and a deployment is started.
          body:
            application/json:
              type: deploymentResult.DeploymentResult
              example: !include examples/deployments_result.json
        404:
          description: No task found with this `app_id`.
          body:
            application/json:
              type: error.Error
              example: |
                  { "message": "App '/not_existent' does not exist" }
        400:
          description: The application definition provided in the body is not valid.
          body:
            application/json:
              type: error.Error
              example: |
                {"message":"Invalid JSON","details":[{"path":"/id","errors":["error.expected.jsstring"]}]}
        422:
          description: The entity sent can not be preocessed, since there are validation errors
          body:
            application/json:
              type: error.Error
              example: |
                {
                  "message": "Object is not valid",
                  "details": [
                    {
                      "path": "/upgradeStrategy/minimumHealthCapacity",
                      "errors": [
                        "is greater than 1"
                      ]
                   }
                  ]
                }

    ###
    # Apply a patch update to a specific app.
    #
    patch:
      description:
        Replaces parameters of a running application. Instances of this application will be started or restarted
        according to the usual logic to meet the requirements of the new definition. Usually, restart is required
        if the application configuration was changed (except for scaling changes).
        Any given application ID will be ignored.

        Note:  This operation will create a deployment. The operation finishes, if the deployment succeeds.
         You can query the deployments endoint to see the status of the deployment.
      is: [ secured, deployable ]
      queryParameters:
      body:
        application/json:
          example: !include examples/app_patch.json
          type: app.App
      responses:
        200:
          description: The application has been updated and a deployment is started.
          body:
            application/json:
              type: deploymentResult.DeploymentResult
              example: !include examples/deployments_result.json
        404:
          description: No task found with this `app_id`.
          body:
            application/json:
              type: error.Error
              example: |
                  { "message": "App '/not_existent' does not exist" }
        400:
          description: The application definition provided in the body is not valid.
          body:
            application/json:
              type: error.Error
              example: |
                {"message":"Invalid JSON","details":[{"path":"/id","errors":["error.expected.jsstring"]}]}
        422:
          description: The entity sent can not be preocessed, since there are validation errors
          body:
            application/json:
              type: error.Error
              example: |
                {
                  "message": "Object is not valid",
                  "details": [
                    {
                      "path": "/upgradeStrategy/minimumHealthCapacity",
                      "errors": [
                        "is greater than 1"
                      ]
                   }
                  ]
                }

    ###
    # Delete a specific app
    #
    delete:
      description: Destroy an application. All data about that application will be deleted.

        Note:  This operation will create a deployment. The operation finishes, if the deployment succeeds.
        You can query the deployments endoint to see the status of the deployment.
      is: [ secured, deployable ]
      responses:
        404:
          description: No app with this id known.
          body:
            application/json:
              type: error.Error
              example: |
                {"message":"App '/not-existing' does not exist"}

    /restart:
      ###
      # Restart this application
      #
      post:
        description: Restart all tasks of this application.
        is: [ secured, deployable ]
        responses:
          404:
            description: No task found with this `app_id`.
            body:
              application/json:
                type: error.Error
                example: |
                  { "message": "App '/not_existent' does not exist" }

    /tasks:
      ###
      # Get all tasks of an application
      #
      get:
        description: List all running tasks for application `app_id`.
        is: [ secured ]
        responses:
          200:
            description: The list of running tasks for application `app_id`.
            body:
              application/json:
                type: task.TaskList
                example: !include examples/app_tasks.json
              text/plain:
                example: |
                    minecraft_survival-world 10013 srv7.hw.ca1.mesosphere.com:31756
          404:
            description: No task found with this `app_id`.
            body:
              application/json:
                example: |
                  { "message": "App '/not_existent' does not exist" }

      ###
      # Kill tasks of an application
      #
      delete:
        description: Kill tasks that belong to the application `app_id`
        is: [ secured, deployable ]
        queryParameters:
          host:
            description: all tasks of that application on the supplied slave are killed
          scale:
            description: If `scale=true` is specified, then the application is scaled down by the number of killed tasks. Only possible if `wipe=false` or not specified.
            default: "false"
          wipe:
            description: If `wipe=true` is specified and the app uses local persistent volumes, associated dynamic reservations will be unreserved, and persistent volumes will be destroyed. Only possible if `scale=false` or not specified.
            default: "false"
        responses:

          200:
            description: If scale=false, all tasks that were killed are returned.
              If scale=true, than a deployment is triggered and the deployment is returned.
            body:
              application/json:
                type: task.TaskList | deploymentResult.DeploymentResult
                example: !include examples/app_tasks.json
          404:
            description: No task found with this `app_id`.
            body:
              application/json:
                example: |
                  { "message": "App '/not_existent' does not exist" }

      /{task_id}:
        ###
        # Delete a single task
        #
        delete:
          description: Kill the task with ID `task_id` that belongs to the application `app_id`.
          is: [ secured, deployable ]
          queryParameters:
            scale:
              description: If `scale=true` is specified, then the application is scaled down by the number of killed tasks. Only possible if `wipe=false` or not specified.
              default: "false"
            wipe:
              description: If `wipe=true` is specified and the app uses local persistent volumes, associated dynamic reservations will be unreserved, and persistent volumes will be destroyed. Only possible if `scale=false` or not specified.
              default: "false"
          responses:
            200:
              description: If scale=false, the task that was killed is returned.
                If scale=true, than a deployment is triggered and the deployment is returned.
              body:
                application/json:
                  type: task.TaskSingle | deploymentResult.DeploymentResult
                  example: !include examples/app_task.json
            404:
              description: No task found with this task_id.
              body:
                application/json:
                  type: error.Error
                  example: |
                    {"message":"Task 'not-existing' does not exist"}

    ###
    # List versions
    #
    /versions:
      get:
        description: List the versions of the application with id `app_id`
        is: [ secured ]
        responses:
          200:
            description: The list of versions of the application
            body:
              application/json:
                example: |
                  { "versions": [ "2014-03-01T23:42:20.938Z" ] }
          404:
            description: No task found with this `app_id`.
            body:
              application/json:
                type: error.Error
                example: |
                  { "message": "App '/not_existent' does not exist" }

      /{version}:
        get:
          description: List the configuration of the application with id `app_id` at version `version`.
          is: [ secured ]
          responses:
            200:
              description: The application definition at that point in time.
              body:
                application/json:
                  type: app.App
                  example: !include examples/app.json
            404:
              description: No task found with this `app_id`.
              body:
                application/json:
                  example: |
                    { "message": "App '/not_existent' does not exist" }


doc: api docs

doc: api docs

fatal: unable to access 'https://github.com/victorhaggqvist/ledman.git/': The requested URL returned error: 403


updated listservices raml

updated listservices raml

remote: Support for password authentication was removed on August 13, 2021.
remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
fatal: Authentication failed for 'https://github.com/Jumpscale/ays9.git/'


Api file

Api file

remote: Support for password authentication was removed on August 13, 2021.
remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
fatal: Authentication failed for 'https://github.com/zero-os/0-orchestrator.git/'


api.raml

api.raml

#%RAML 1.0
title: Backend API
version: v0.1
baseUri: http://localhost:
mediaType:  application/json

/classificators:
  get:
    description: |
     Возвращает результат по полнотекстовому поиску сразу по всем классификаторам
    queryParameters:
      queryParameters:
        query:
          description: "Запрос для полнотекстового поиска по  всем классификаторам"
          type: string
          required: true
          example: "оленьи рога"
      responses:
        200:
          body:
            application/json:
              example: |
                [
                  {
                    okpd: {
                      code: "01",
                      parentCode: null,
                      name: "",
                      notes: null,
                      hasChildren: true,
                    },
                    okpd2: {
                      code: "01",
                      parentCode: null,
                      name: "",
                      notes: null,
                      hasChildren: true,
                    },
                    tnved: {
                      code: "01",
                      parentCode: null,
                      name: "",
                      notes: null,
                      hasChildren: true
                    }
                  },
                  okpd: {
                      code: "01",
                      parentCode: null,
                      name: "",
                      notes: null,
                      hasChildren: true
                    },
                    okpd2: {
                      code: "01",
                      parentCode: null,
                      name: "",
                      notes: null,
                      hasChildren: true
                    },
                    tnved: {
                      code: "01",
                      parentCode: null,
                      name: "",
                      notes: null,
                      hasChildren: true
                    }
                  }
                ]

  /okpd:
    get:
      description: |
        Дерево классификатора. Пока нужно получать только потомков 1го уровня от корня с кодом code.
      queryParameters:
        code:
          description: "Код окпд"
          type: string
          required: false
          example: "01"
      responses:
        200:
          body:
            application/json:
              example: |
                [
                  {
                    "code":"01",
                    "name":"Продукция и услуги сельского хозяйства и охоты",
                    "notes":null,
                    "parentCode":null,
                    "hasChildren":true
                  },
                  {
                    "code":"02",
                    "name":"Продукция лесоводства, лесозаготовок и связанные с этим услуги",
                    "notes":null,
                    "level":1,
                    "parentCode":null,
                    "hasChildren":true
                  }
                ]
  /okpd2:
    get:
      description: |
        Сlassificators tree
      queryParameters:
        code:
          description: "Код окпд2"
          type: string
          required: false
          example: "01"
      responses:
        200:
          body:
            application/json:
              example: |
                [
                  {
                    "code":"01",
                    "name":"Продукция и услуги сельского хозяйства и охоты",
                    "notes":null,
                    "parentCode":null,
                    "hasChildren":true
                  },
                  {
                    "code":"02",
                    "name":"Продукция лесоводства, лесозаготовок и связанные с этим услуги",
                    "notes":null,
                    "level":1,
                    "parentCode":null,
                    "hasChildren":true
                  }
                ]
  /tnved:
    get:
      description: |
        Сlassificators tree
      queryParameters:
        code:
          description: "Код ТНВЭД"
          type: string
          required: false
          example: "01"
      responses:
        200:
          body:
            application/json:
              example: |
                [
                  {
                    "code":"01",
                    "name":"Продукция и услуги сельского хозяйства и охоты",
                    "notes":null,
                    "parentCode":null,
                    "hasChildren":true
                  },
                  {
                    "code":"02",
                    "name":"Продукция лесоводства, лесозаготовок и связанные с этим услуги",
                    "notes":null,
                    "level":1,
                    "parentCode":null,
                    "hasChildren":true
                  }
                ]

error: pathspec 'api.raml' did not match any file(s) known to git


Update gateway definition (#331)

Update gateway definition (#331)

Signed-off-by: Jo De Boeck <8aae4f96b4b8e986d268fd26b5ab7bae28223566@gmail.com>


readds interface file

readds interface file

#%RAML 0.8
title: "Janelia Service Handler"
version: v1
baseUri: /
/services:
  get:
  /services/{service}
    get:
/nodes:
  get:

error: pathspec 'interface/interface.raml' did not match any file(s) known to git


Added api first draft

Added api first draft

#%RAML 0.8
title: ChewCrew
version: v1
baseUri: http://chewcrew.io/{version}

/preferences:
  /categories:
    get:
      description: Only display category type preferences (BBQ, Chinese, Pizza, etc.)

/sessions:
  post:
    description: Create a voting session
    queryParameters:

  /{id}:
    /start:
      post:
        description: Starts the voting session
    /end:
      post:
        description: Forcefully ends a voting session
    get:
      description: Retrieve a voting session
      responses:
        200:
          body:
            application/json:
              schema: |
                {
                "$schema": "http://json-schema.org/schema",
                "type": "object",
                "description": "A voting session",
                "properties": {
                "voters": "Total number of unique voters participating",
                "voters": {
                  "type": "array",
                  "name": {"type": "string"}
                  },
                "voted": "Total number of current votes",
                "voted": {"type": "int"},
                "choices": "Will be populated once the voting session has started",
                "choices": {
                  "type": "array",
                  "items": {"type" : "string"},
                  "minItems": 3,
                  "uniqueItems": true
                  },
                "result": "The winning result. Will be populating once all voters have voted.",
                "result": {"type": "string"}
                }}
    put:
      description: Update a voting session (will be done when voters first enter a session)
      queryParameters:
        name:
          description: Voters name
        preferences:
          description: Preferences to add
        location:
          description: Location to add
    post:
      description: Submit a vote to a voting session
      queryParameters:
        choice:
          description: Vote to submit


Fix #423: Document searchstring instead of username in AddMember body

remote: Support for password authentication was removed on August 13, 2021.
remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
fatal: Authentication failed for 'https://github.com/itsyouonline/identityserver.git/'


Fix #435: Generated go client does not compile

remote: Support for password authentication was removed on August 13, 2021.
remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
fatal: Authentication failed for 'https://github.com/lucasvanhalst/identityserver.git/'


fix grammar error in security.raml

fix grammar error in security.raml

remote: Support for password authentication was removed on August 13, 2021.
remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
fatal: Authentication failed for 'https://github.com/simonsdave/cloudfeaster-services.git/'


Set display names

Set display names


minor update to index.raml in api docs

minor update to index.raml in api docs


Fix attribute types.

Fix attribute types.


Two-space indent (FOLIO-351)

Two-space indent (FOLIO-351)

remote: Support for password authentication was removed on August 13, 2021.
remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
fatal: Authentication failed for 'https://github.com/craigmcnally/mod-users.git/'


Stated outlining/documenting the REST API in RAML format.

#%RAML 0.8

title: Mulgrew
version: v1
protocols: [ HTTPS ]
baseUri: https://api.tunk.io/{version}
mediaType: application/json
securitySchemes:
    - oauth_2_0:
        description: |
            Dropbox supports OAuth 2.0 for authenticating all API requests.
        type: OAuth 2.0
        describedBy:
            headers:
                Authorization:
                    description: |
                       Used to send a valid OAuth 2 access token. Do not use
                       with the "access_token" query string parameter.
                    type: string
            queryParameters:
                access_token:
                    description: |
                       Used to send a valid OAuth 2 access token. Do not use together with
                       the "Authorization" header
                    type: string
            responses:
                401:
                    description: |
                        Bad or expired token. This can happen if the user or Dropbox
                        revoked or expired an access token. To fix, you should re-
                        authenticate the user.
                403:
                    description: |
                        Bad OAuth request (wrong consumer key, bad nonce, expired
                        timestamp...). Unfortunately, re-authenticating the user won't help here.
        settings:
          authorizationUri: https://www.dropbox.com/1/oauth2/authorize
          accessTokenUri: https://api.dropbox.com/1/oauth2/token
          authorizationGrants: [ code, token ]

/notebook:
  /new:
    securedBy: [oauth_2_0]
    post:
  /{id}:
    securedBy: [oauth_2_0]
    get:
      queryParameters:
        token:
          type: string
          required: true
    post:
    delete:
  /list:
    securedBy: [oauth_2_0]
    get:
  /add:
    /note:
      /{id}:
        securedBy: [oauth_2_0]
        post:
/note:
  /new:
    securedBy: [oauth_2_0]
    post:
      queryParameters:
        title:
        text:
  /{id}:
    securedBy: [oauth_2_0]
    get:
    post:
      queryParameters:
        title:
        text:
    delete:
  /list:
    securedBy: [oauth_2_0]
    get:
/tags:
  get:
    queryParameters:
      term:
      sort:
/user:
  /new:
    post:
  /{id}:
    get:
    delete:
    post:
/signin:
  post:


Update docstring for templatevdisk

Update docstring for templatevdisk

Signed-off-by: Jo De Boeck <8aae4f96b4b8e986d268fd26b5ab7bae28223566@gmail.com>


replace actions.py with actions_py in specs/api.raml


Fix url for UserIsMember endpoint

Fix url for UserIsMember endpoint


api doku created

api doku created

#%RAML 0.8

title: JailService API
baseURI: http://example.api.com
version: 01

/jail:
 	post:
 		description: create a player
 			body:
 				application/json:
 					schema: |
 						{
 							"type": "object",
                  			"properties": {
                    			"playerId":  { "type": "string" }
 						}
 					example: |
 					{
 						"playerId": "abc",
 					}
 		responses:
			201:
				schema: |
 						{
 							"type": "object",
                  			"properties": {
                    			"playerId":  { "type": "string" },
                    			"roundsInJail": { "type": "number" },
                    			"isInJail": { "type": "boolean" }
 						}
 		responses:
			420:
				schema: |
 						{
 							"type": "object",
                  			"properties": {
                    			"playerId":  "Not created. PlayerId was missing",
                    			"roundsInJail":  0,
                    			"isInJail": false
 						}

/{playerId}:
	get:
		description: get a player by Id
		responses:
			200:
 				body:
 					application/json:
 						schema: |
 						{
 							"type": "object",
                  			"properties": {
                    			"playerId":  { "type": "string" },
                    			"roundsInJail": { "type": "number" },
                    			"isInJail": { "type": "boolean" }
 						}
 						example: |
 						{
 							"playerId": "abc",
 							"roundsInJail":0,
 							"isInJail":false
 						}
 			404:
 				description: not found
	post:
		description: player rolls the dices
		queryParameters: pasch
			type: boolean
			description: whether the dices are a pasch
			requiered: true
		responses:
			200:
 				body:
 					application/json:
	 					schema: |
 						{
 							"type": "object",
                  			"properties": {
                    			"playerId":  { "type": "string" },
                    			"roundsInJail": { "type": "number" },
                    			"isInJail": { "type": "boolean" }
 						}
						example: |
 						{
 							"playerId": "abc",
 							"roundsInJail":0,
 							"isInJail":false
 						}
 			420:
 				description: no query param is set
 					schema: |
 					{
 						"type": "object",
                  		"properties": {
                    		"playerId":  "Pasch query param must be set",
                    		"roundsInJail":  0,
                    		"isInJail": false
 					}
 			404:
 				description: playerId doesnt exist
 					schema: |
 					{
 						"type": "object",
                  		"properties": {
                    		"playerId":  "not found",
                    		"roundsInJail":  0,
                    		"isInJail": false
 					}

error: pathspec 'RESTopoly/jail_api.raml' did not match any file(s) known to git


Add type for CreateStoragePoolDevices

Add type for CreateStoragePoolDevices


consumer api for vocab repo in RAML

consumer api for vocab repo in RAML

#%RAML 0.8

title: LinDA Vocabulary Repository API
# baseUri:
version: v1
# documentation:

/vocab:
  get:
    queryParameters:
      uri:
        type: string
        required: true
    responses:
      200:
        body:
          application/xml:
          text/turtle:
          text/n3:
  /search:
    # is: [paged]
    get:
      queryParameters:
        q:
          type: string
          required: true
      responses:
        200:
          body:
            application/json:
              schema: |
                {
                  "$schema": "http://json-schema.org/schema",
                  "type": "collection",
                  "properties": {
                    "prefix":  { "type": "string" },
                    "namespace": { "type": "string" },
                    "score": { "type": "string" }
                  },
                  "required": [ "prefix", "namespace", "score" ]
                }

/classes:
  /search:
    # is: [paged]
    get:
      queryParameters:
        q:
          type: string
          required: true
        vocab:
          type: string
          required: false
      responses:
        200:
          body:
            application/json:
              schema: |
                {
                  "$schema": "http://json-schema.org/schema",
                  "type": "collection",
                  "properties": {
                    "uri": { "type": "string" },
                    "prefix":  { "type": "string" },
                    "namespace": { "type": "string" },
                    "localName": { "type": "string" },
                    "score": { "type": "string" }
                  },
                  "required": [ "prefix", "namespace", "score" ]
                }
              example: |

/properties:
  /search:
    # is: [paged]
    get:
      queryParameters:
        q:
          type: string
          required: true
        vocab:
          type: string
          required: false
      responses:
        200:
          body:
            application/json:
              schema: |
                {
                  "$schema": "http://json-schema.org/schema",
                  "type": "collection",
                  "properties": {
                    "uri": { "type": "string" },
                    "prefix":  { "type": "string" },
                    "namespace": { "type": "string" },
                    "localName": { "type": "string" },
                    "score": { "type": "string" }
                  },
                  "required": [ "prefix", "namespace", "score" ]
                }
              example: |

error: pathspec 'server/resource/public/api/vocab-repo.raml' did not match any file(s) known to git


Fix ramle syntax

Fix ramle syntax


remove traits & resource type in tutorial.raml file:

- it use inline resource type : go-raml & api-console doesn't support it
- it use traits that are not defined

remote: Support for password authentication was removed on August 13, 2021.
remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
fatal: Authentication failed for 'https://github.com/Jumpscale/go-raml.git/'


Add initial RAML spec.

Add initial RAML spec.

- Currently has models and a couple of the needed routes.

Signed-off-by: Mark Stenglein <f1b5a91d4d6ad523f2610114591c007e75d15084@stengle.in>

#%RAML 1.0
---
title: schedules
description: Documentation for the Schedules API.
version: v2
baseUri: https://schedules.gmu.edu/api/{version}
protocols: [ HTTP, HTTPS ]
mediaType: [application/json, application/ical]

types:
  Campus:
    type: object
    properties:
      slug:
        required: true
        type: string
      name:
        required: true
        type: string
      address:
        required: true
        type: string
      timezone:
        required: true
        type: string

  Semester:
    type: object
    properties:
      slug:
        required: true
        type: string
      name:
        required: true
        type: string
        pattern: /^Fall|Winter|Spring|Summer$/
      year:
        required: true
        type: string

  Semesters:
    type: Semester[]
    minItems: 0
    uniqueItems: true
    displayName: Semesters

  Course:
    type: object
    properties:
      slug:
        required: true
        type: string
      name:
        required: true
        type: string

  Courses:
    type: Course[]
    minItems: 0
    uniqueItems: true

  Session:
    type: object
    properties:
      location:
        required: true
        type: Campus # Contains timezone information
      days:
        required: true
        type: string[]
        example:
          - "MON"
          - "TUES"
          - "WED"
          - "THURS"
          - "FRI"
          - "SAT"
          - "SUN"
      startTime:
        required: true
        type: time-only
      endTime:
        required: true
        type: time-only

  Sessions:
    type: Session[]
    minItems:  0
    uniqueItems: true

  Section:
    type: object
    properties:
      course:
        required: true
        type: Course
      sessions:
        required: true
        type: Sessions
      professor:
        required: false
        type: string
      class_type:
        required: true
        type: string
      #Start - End Date included in Semester

  Sections:
    type: Section[]
    minItems: 0
    uniqueItems: true

/semesters:
  get:
  /{semesterSlug}:
    get:
    /{page}:

/courses:
  get:
    queryParameters:
      semester:
        displayName: Semester
        type: string
        description: >
          The semester slug to pull courses from. Any course which has a
          class which took place in the given semester will be returned.
        example: SP2017 # Spring, 2017
        required: false
      professor:
        displayName: Professor
        type: string
        description: >
          The professor slug to pull courses from. Any course which has ever
          been taught by the given professor will be returned. This should be
          given in the form of a valid netid (for SRCT's implementation at
          least).
        example: mstengle
        required: false

  /{courseSlug}:
    get:

/classes:
  get:

  /{semesterSlug}/{classSlug}:
    get:

/schedule:
  get:
    queryParameters:
      classes:
        displayName: Classes Taken
        type: string[]
        uniqueItems: true
        minItems: 1
        description: >
          The classes to compile into one full calendar file. These should be
          given as CRNs (Course Registration Number).
        example:
          - "234567"
          - "234568"
        required: true
      semester:
        displayName: Semester
        type: string
        description: >
          The semester for which the calendar should be generated for. While
          optional, this setting will cause the service to validate the CRNs
          to be sure that the classes selected all take place in the
          selected semester.
        example: SP2017 # Spring, 2017
        required: false

error: pathspec 'schedules.raml' did not match any file(s) known to git