Files
zeekay 189ce08e51 Regenerate against the document the deployment answers for
The projection these were generated from was a month old and predated the
compute migration, so every one of them described /v1/visor — which the API
serves at zero paths now. That is why a hand-written console client and a
generated one had drifted the same way at the same time.

No /v1/visor path survives here. The word still appears as a source-plane
value and inside gvisor and supervisor, which are not this rename.
2026-09-05 18:07:13 -07:00

129 lines
3.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.
*/
/*
* Check.h
*
*
*/
#ifndef HANZO_MODEL_Check_H_
#define HANZO_MODEL_Check_H_
#include <boost/optional.hpp>
#include "hanzo/ModelBase.h"
#include <cpprest/details/basic_types.h>
namespace hanzo {
namespace model {
class Check
: public ModelBase
{
public:
Check();
virtual ~Check();
/////////////////////////////////////////////
/// 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;
/////////////////////////////////////////////
/// Check members
utility::datetime getAt() const;
bool atIsSet() const;
void unsetAt();
void setAt(const utility::datetime& value);
/// <summary>
/// Job is the job that decided State. A run reports one conclusion for however many jobs it holds, and the jobs are not interchangeable: the pipeline fails at &#x60;gate&#x60; before it builds anything and at &#x60;receipt&#x60; after it has already built, pinned and proved the release live. Both read &#x60;failure&#x60; on the run, and only the first one means nothing shipped.
/// </summary>
utility::string_t getJob() const;
bool jobIsSet() const;
void unsetJob();
void setJob(const utility::string_t& value);
int64_t getNumber() const;
bool numberIsSet() const;
void unsetnumber();
void setNumber(int64_t value);
/// <summary>
/// State is success | failure | running | absent. &#x60;absent&#x60; is not a kind of failure and is kept apart from one: a failing run is a build that ran and said no, while an absent run is Hanzo Git never having constructed a run for the commit at all — a workflow it cannot parse or a reference it cannot resolve. There is no log to open for the second, so a page that draws them the same sends you looking for one that does not exist.
/// </summary>
utility::string_t getState() const;
bool stateIsSet() const;
void unsetState();
void setState(const utility::string_t& value);
/// <summary>
/// Tested reports that the run&#39;s tests executed; Verdict reports that the run said anything about tests at all. They are separate because the interesting case is a run that passed while its test step was skipped — a green build that proved nothing — and that is invisible if the two are one flag.
/// </summary>
bool isTested() const;
bool testedIsSet() const;
void unsetTested();
void setTested(bool value);
utility::string_t getUrl() const;
bool urlIsSet() const;
void unsetUrl();
void setUrl(const utility::string_t& value);
bool isVerdict() const;
bool verdictIsSet() const;
void unsetVerdict();
void setVerdict(bool value);
protected:
utility::datetime m_At;
bool m_AtIsSet;
utility::string_t m_Job;
bool m_JobIsSet;
int64_t m_number;
bool m_numberIsSet;
utility::string_t m_State;
bool m_StateIsSet;
bool m_Tested;
bool m_TestedIsSet;
utility::string_t m_Url;
bool m_UrlIsSet;
bool m_Verdict;
bool m_VerdictIsSet;
};
}
}
#endif /* HANZO_MODEL_Check_H_ */