mirror of
https://github.com/hanzo-cpp/sdk.git
synced 2026-11-20 19:55:32 +00:00
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.
222 lines
6.6 KiB
C++
222 lines
6.6 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.
|
|
*/
|
|
|
|
/*
|
|
* RunnerBuildReq.h
|
|
*
|
|
*
|
|
*/
|
|
|
|
#ifndef HANZO_MODEL_RunnerBuildReq_H_
|
|
#define HANZO_MODEL_RunnerBuildReq_H_
|
|
|
|
#include <boost/optional.hpp>
|
|
|
|
#include "hanzo/ModelBase.h"
|
|
|
|
#include "hanzo/model/BinarySpec.h"
|
|
#include <cpprest/details/basic_types.h>
|
|
#include <map>
|
|
#include <vector>
|
|
|
|
namespace hanzo {
|
|
namespace model {
|
|
|
|
class BinarySpec;
|
|
|
|
|
|
class RunnerBuildReq
|
|
: public ModelBase
|
|
{
|
|
public:
|
|
RunnerBuildReq();
|
|
virtual ~RunnerBuildReq();
|
|
|
|
/////////////////////////////////////////////
|
|
/// 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;
|
|
|
|
|
|
/////////////////////////////////////////////
|
|
/// RunnerBuildReq members
|
|
|
|
|
|
/// <summary>
|
|
/// Arch is the target architecture for the artifact lane.
|
|
/// </summary>
|
|
utility::string_t getArch() const;
|
|
bool archIsSet() const;
|
|
void unsetArch();
|
|
void setArch(const utility::string_t& value);
|
|
|
|
/// <summary>
|
|
/// Args are --build-arg values. They are what lets several images off ONE Dockerfile mean different things — the sandbox classes are three entries differing only by STAGE. Validated at the k8s choke point, with VERSION and REVISION taking precedence: those are receipts the builder derives from the tag and the commit, and a caller that could overwrite them could make an image lie about which commit it is.
|
|
/// </summary>
|
|
std::map<utility::string_t, utility::string_t> getArgs() const;
|
|
bool argsIsSet() const;
|
|
void unsetArgs();
|
|
void setArgs(const std::map<utility::string_t, utility::string_t>& value);
|
|
|
|
/// <summary>
|
|
/// Binaries selects the ARTIFACT lane (artifact.go): build what the repo's hanzo.yml `binaries:` block declares — a Go binary, an npm tarball, a Rust binary — and publish it to hanzoai/s3 instead of pushing an image. It is the same recipe hanzoai/ci reads, sent verbatim, so `image` is meaningless here and must be absent.
|
|
/// </summary>
|
|
std::vector<std::shared_ptr<BinarySpec>> getBinaries() const;
|
|
bool binariesIsSet() const;
|
|
void unsetBinaries();
|
|
void setBinaries(const std::vector<std::shared_ptr<BinarySpec>>& value);
|
|
|
|
/// <summary>
|
|
/// Branch is the branch to build when no SHA or Ref is given.
|
|
/// </summary>
|
|
utility::string_t getBranch() const;
|
|
bool branchIsSet() const;
|
|
void unsetBranch();
|
|
void setBranch(const utility::string_t& value);
|
|
|
|
/// <summary>
|
|
/// Bucket mirrors hanzo.yml's `bucket:` — where the artifact lane publishes.
|
|
/// </summary>
|
|
utility::string_t getBucket() const;
|
|
bool bucketIsSet() const;
|
|
void unsetBucket();
|
|
void setBucket(const utility::string_t& value);
|
|
|
|
/// <summary>
|
|
/// Context is the build context path within the repo.
|
|
/// </summary>
|
|
utility::string_t getContext() const;
|
|
bool contextIsSet() const;
|
|
void unsetContext();
|
|
void setContext(const utility::string_t& value);
|
|
|
|
/// <summary>
|
|
/// DockerTarget is the multi-stage build target to stop at.
|
|
/// </summary>
|
|
utility::string_t getDockerTarget() const;
|
|
bool dockerTargetIsSet() const;
|
|
void unsetDockerTarget();
|
|
void setDockerTarget(const utility::string_t& value);
|
|
|
|
/// <summary>
|
|
/// Dockerfile is the path to build from; empty uses the zero-config frontend.
|
|
/// </summary>
|
|
utility::string_t getDockerfile() const;
|
|
bool dockerfileIsSet() const;
|
|
void unsetDockerfile();
|
|
void setDockerfile(const utility::string_t& value);
|
|
|
|
/// <summary>
|
|
/// Image is the output image ref to push. Required on the image lane, and it must target a registry namespace the caller's org owns.
|
|
/// </summary>
|
|
utility::string_t getImage() const;
|
|
bool imageIsSet() const;
|
|
void unsetImage();
|
|
void setImage(const utility::string_t& value);
|
|
|
|
/// <summary>
|
|
/// OS is the target operating system for the artifact lane.
|
|
/// </summary>
|
|
utility::string_t getOs() const;
|
|
bool osIsSet() const;
|
|
void unsetOs();
|
|
void setOs(const utility::string_t& value);
|
|
|
|
/// <summary>
|
|
/// Ref is the git ref to build when no SHA is given.
|
|
/// </summary>
|
|
utility::string_t getRef() const;
|
|
bool refIsSet() const;
|
|
void unsetRef();
|
|
void setRef(const utility::string_t& value);
|
|
|
|
/// <summary>
|
|
/// Repo is the repository clone URL to build. Required on the image lane.
|
|
/// </summary>
|
|
utility::string_t getRepo() const;
|
|
bool repoIsSet() const;
|
|
void unsetRepo();
|
|
void setRepo(const utility::string_t& value);
|
|
|
|
/// <summary>
|
|
/// SHA is the commit to pin; it wins over Ref and Branch.
|
|
/// </summary>
|
|
utility::string_t getSha() const;
|
|
bool shaIsSet() const;
|
|
void unsetSha();
|
|
void setSha(const utility::string_t& value);
|
|
|
|
/// <summary>
|
|
/// Tag is the publish path segment, so both entry points write ONE index at ONE URL. It defaults to the pinned ref, and must be named explicitly for a branch.
|
|
/// </summary>
|
|
utility::string_t getTag() const;
|
|
bool tagIsSet() const;
|
|
void unsetTag();
|
|
void setTag(const utility::string_t& value);
|
|
|
|
|
|
protected:
|
|
utility::string_t m_Arch;
|
|
bool m_ArchIsSet;
|
|
|
|
std::map<utility::string_t, utility::string_t> m_Args;
|
|
bool m_ArgsIsSet;
|
|
|
|
std::vector<std::shared_ptr<BinarySpec>> m_Binaries;
|
|
bool m_BinariesIsSet;
|
|
|
|
utility::string_t m_Branch;
|
|
bool m_BranchIsSet;
|
|
|
|
utility::string_t m_Bucket;
|
|
bool m_BucketIsSet;
|
|
|
|
utility::string_t m_Context;
|
|
bool m_ContextIsSet;
|
|
|
|
utility::string_t m_DockerTarget;
|
|
bool m_DockerTargetIsSet;
|
|
|
|
utility::string_t m_Dockerfile;
|
|
bool m_DockerfileIsSet;
|
|
|
|
utility::string_t m_Image;
|
|
bool m_ImageIsSet;
|
|
|
|
utility::string_t m_Os;
|
|
bool m_OsIsSet;
|
|
|
|
utility::string_t m_Ref;
|
|
bool m_RefIsSet;
|
|
|
|
utility::string_t m_Repo;
|
|
bool m_RepoIsSet;
|
|
|
|
utility::string_t m_Sha;
|
|
bool m_ShaIsSet;
|
|
|
|
utility::string_t m_Tag;
|
|
bool m_TagIsSet;
|
|
|
|
};
|
|
|
|
|
|
}
|
|
}
|
|
|
|
#endif /* HANZO_MODEL_RunnerBuildReq_H_ */
|