Versions

Saves every file of the lambda as a new version

files is the whole lambda, lambda.cs first: a file the newest version has and this request does not is not in the new version. To change a few files, POST …/versions/changes sends only those.

A file name may be refused - a C# file has to be named as C# names its files, a resource needs an extension, and no name may hold spaces or be one Windows reserves; the message says what is wrong with which. The files together may not come to more than the tier of the lambda allows a version (see the limits). Whether the code compiles is not checked unless it is deployed: POST …/code/check compiles it without saving.

post/lambdas/{privateKey}/versions

Request

  • Base URL: https://genhttp.dev/api/v1
  • URL: https://genhttp.dev/api/v1/lambdas/{privateKey}/versions
  • Auth: none declared

Path parameters

privateKeystring required

The editor key of the lambda. Holding it is what allows the call.

Query parameters

deployboolean

Whether to put the new version online as well. The version is saved either way; whether it went online is in deployment.

Request body

Specificationstring nullable

What the user wants from this version and why - their requirements, in their own words where possible. Optional, and cut past 4000 characters.

Changestring nullable

What this version changes, in one line for the owner. Optional, and cut past 500 characters.

Response

The version was saved. If it was to be deployed as well, deployment says whether that worked.

Versioninteger

Its number

Createdstring date-time

When it was saved

Specificationstring nullable

What the user wanted and why, as it was kept

Changestring nullable

What it changes, as it was kept

Originstring nullable

How it was saved

Changes

No recorded changes to this operation across all 1 revision of this API.