Files
zeekay 645325a641 regenerate from cloud 939b09d4
The projection was 113 commits behind the document it claims to describe, and
`generate.py --all --check` reported every one of the thirteen clients DRIFTED —
the same +19 models in each, because they all fell behind the same emission.

Regenerated in place from hanzo-inc/cloud openapi.yaml at 939b09d4
(sha256 087024f6…), which is the only description of this API that cannot name a
route the binary does not serve. `--check` is clean across all thirteen after.

.spec-lock moved with the code. The generator READS that file and never writes
it — hanzoai/ci`s lane does — so a hand run leaves every lock naming the previous
document. A lock that disagrees with the tree beside it is worse than no lock:
the next `--check` without `--spec` fetches what production serves, compares it
to a digest that was already wrong, and reports drift that is really staleness.
2026-08-24 23:32:53 -07:00

142 lines
4.7 KiB
C++

/**
* Hanzo Cloud API
* The Hanzo Cloud API as a customer calls it: every operation under /v1/ except the operator's admin product, relay routes, legacy spellings and capabilities still reached by flag. Tagged by product: the first path segment after /v1/.
*
* The version of the OpenAPI document: v1
*
* NOTE: This class is auto generated by OpenAPI-Generator 7.14.0.
* https://openapi-generator.tech
* Do not edit the class manually.
*/
/*
* BinarySpec.h
*
*
*/
#ifndef HANZO_MODEL_BinarySpec_H_
#define HANZO_MODEL_BinarySpec_H_
#include <boost/optional.hpp>
#include "hanzo/ModelBase.h"
#include <cpprest/details/basic_types.h>
#include <vector>
namespace hanzo {
namespace model {
class BinarySpec
: public ModelBase
{
public:
BinarySpec();
virtual ~BinarySpec();
/////////////////////////////////////////////
/// ModelBase overrides
void validate() override;
web::json::value toJson() const override;
bool fromJson(const web::json::value& json) override;
void toMultipart(std::shared_ptr<MultipartFormData> multipart, const utility::string_t& namePrefix) const override;
bool fromMultiPart(std::shared_ptr<MultipartFormData> multipart, const utility::string_t& namePrefix) override;
/////////////////////////////////////////////
/// BinarySpec members
/// <summary>
/// Image is the toolchain image the recipe runs in, a Go bookworm image by default. It is the one field the GitHub lane ignores: there the runner IS the toolchain, and a cluster has to be told what a runner already is.
/// </summary>
utility::string_t getImage() const;
bool imageIsSet() const;
void unsetImage();
void setImage(const utility::string_t& value);
/// <summary>
/// Ldflags are the Go linker flags, &#x60;-s -w&#x60; when the recipe names none, on one line. Go lane only.
/// </summary>
utility::string_t getLdflags() const;
bool ldflagsIsSet() const;
void unsetLdflags();
void setLdflags(const utility::string_t& value);
/// <summary>
/// Main is the Go package to build, repo-relative (&#x60;.&#x60; or &#x60;./cmd/x&#x60;), and it selects the GO LANE. Defaults to &#x60;.&#x60; when neither lane is named; declaring it together with &#x60;run&#x60; is refused.
/// </summary>
utility::string_t getMain() const;
bool mainIsSet() const;
void unsetMain();
void setMain(const utility::string_t& value);
/// <summary>
/// Name is the artifact&#39;s base name: the prefix of every file published for this entry, and the name a host later asks for. It must match &#x60;^[A-Za-z0-9][A-Za-z0-9._-]{0,63}$&#x60;, which is what makes it safe as both a filename and a URL path segment.
/// </summary>
utility::string_t getName() const;
bool nameIsSet() const;
void unsetName();
void setName(const utility::string_t& value);
/// <summary>
/// Out is the glob of files &#x60;run&#x60; produced, relative to the repo root; matching nothing FAILS the build rather than publishing an empty entry. It expands unquoted, so it is bounded to path and glob characters. The Go lane names its own files and ignores this.
/// </summary>
utility::string_t getOut() const;
bool outIsSet() const;
void unsetOut();
void setOut(const utility::string_t& value);
/// <summary>
/// Platforms are the &#x60;&lt;os&gt;/&lt;arch&gt;&#x60; pairs the Go lane cross-compiles, [linux/amd64] by default. Each one publishes as &#x60;&lt;name&gt;-&lt;os&gt;-&lt;arch&gt;&#x60;, which is the shape a host resolves a binary BY — so the list is what a caller can ask for later.
/// </summary>
std::vector<utility::string_t> getPlatforms() const;
bool platformsIsSet() const;
void unsetPlatforms();
void setPlatforms(const std::vector<utility::string_t>& value);
/// <summary>
/// Run is any other toolchain&#39;s build command, run by &#x60;sh -c&#x60; in this entry&#39;s image, and it selects the OTHER LANE. Arbitrary shell is the point — it is the same trust as a Dockerfile RUN — which is why it executes with no object-store credential and no service-account token. It requires &#x60;out&#x60;.
/// </summary>
utility::string_t getRun() const;
bool runIsSet() const;
void unsetRun();
void setRun(const utility::string_t& value);
protected:
utility::string_t m_Image;
bool m_ImageIsSet;
utility::string_t m_Ldflags;
bool m_LdflagsIsSet;
utility::string_t m_Main;
bool m_MainIsSet;
utility::string_t m_Name;
bool m_NameIsSet;
utility::string_t m_Out;
bool m_OutIsSet;
std::vector<utility::string_t> m_Platforms;
bool m_PlatformsIsSet;
utility::string_t m_Run;
bool m_RunIsSet;
};
}
}
#endif /* HANZO_MODEL_BinarySpec_H_ */