Saves a zip archive as a new version
The archive replaces every file, so it has to hold all of them: a file it leaves out is not in the new version.
It is read as a commit of the files would be. A single folder around everything is removed. A git repository is skipped, and so is what the .gitignore files in the archive leave out - except files the newest version already has, which are kept as git keeps what it tracks. Other dot files of the code are kept; hidden files among the resources are skipped. Text files are kept as text, anything that is not UTF-8 as base64. With ?layout=project the archive is read as a clone of the lambda's git repository has it, and the platform's own files are left out.
The archive is counted as it is sent, before anything is left out, against what a version may come to. Zip what a commit would hold - never what a build installed (node_modules, for example).
Request
- Base URL: https://genhttp.dev/api/v1
- URL: https://genhttp.dev/api/v1/lambdas/{privateKey}/versions/zip
- Auth: none declared
Path parameters
The editor key of the lambda. Holding it is what allows the call.
Query parameters
Whether to put the new version online as well. The version is saved either way; whether it went online is in deployment.
What the user wants from this version and why, in their words where possible. Kept with the version, cut past 4000 characters.
What this version changes, in one line for the owner. Kept with the version, cut past 500 characters.
How the files are laid out: lambda (the default) names them as the lambda does, project as a clone of its git repository has them - the snippet as Project.cs, the other C# files named the .NET way, the platform's own files left out
Response
The version was saved. If it was to be deployed as well, deployment says whether that worked.
Changes
No recorded changes to this operation across all 1 revision of this API.