Files
sdk/include/hanzo/model/O11y_StatusIncident.h
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

155 lines
5.0 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.
*/
/*
* O11y_StatusIncident.h
*
*
*/
#ifndef HANZO_MODEL_O11y_StatusIncident_H_
#define HANZO_MODEL_O11y_StatusIncident_H_
#include <boost/optional.hpp>
#include "hanzo/ModelBase.h"
#include "hanzo/model/O11y_StatusComponent.h"
#include <cpprest/details/basic_types.h>
#include <vector>
namespace hanzo {
namespace model {
class O11y_StatusComponent;
class O11y_StatusIncident
: public ModelBase
{
public:
O11y_StatusIncident();
virtual ~O11y_StatusIncident();
/////////////////////////////////////////////
/// 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;
/////////////////////////////////////////////
/// O11y_StatusIncident members
/// <summary>
/// AffectedComponents is what this incident covers. It is COUNTED rather than classified: some services down is a partial outage and every probed service down is a full one, because deciding that one service is critical and another is not would need a judgement nobody has measured.
/// </summary>
std::vector<std::shared_ptr<O11y_StatusComponent>> getAffectedComponents() const;
bool affectedComponentsIsSet() const;
void unsetAffected_components();
void setAffectedComponents(const std::vector<std::shared_ptr<O11y_StatusComponent>>& value);
/// <summary>
/// CurrentWorstImpact is the incident&#39;s impact on the PLATFORM, which is not the same question as the component&#39;s own condition above.
/// </summary>
utility::string_t getCurrentWorstImpact() const;
bool currentWorstImpactIsSet() const;
void unsetCurrent_worst_impact();
void setCurrentWorstImpact(const utility::string_t& value);
/// <summary>
/// ID is derived from the service, so the same outage keeps one id across reads rather than being reported as a new incident every 15 seconds.
/// </summary>
utility::string_t getId() const;
bool idIsSet() const;
void unsetId();
void setId(const utility::string_t& value);
/// <summary>
/// LastUpdateAt is when the failing measurement this incident reports was read, RFC3339 UTC.
/// </summary>
utility::string_t getLastUpdateAt() const;
bool lastUpdateAtIsSet() const;
void unsetLast_update_at();
void setLastUpdateAt(const utility::string_t& value);
/// <summary>
/// LastUpdateMessage says what was observed, not what is being done about it — there is no operator writing updates here, only the probe that failed.
/// </summary>
utility::string_t getLastUpdateMessage() const;
bool lastUpdateMessageIsSet() const;
void unsetLast_update_message();
void setLastUpdateMessage(const utility::string_t& value);
/// <summary>
/// Name is the one-line headline, built from the service that stopped answering.
/// </summary>
utility::string_t getName() const;
bool nameIsSet() const;
void unsetName();
void setName(const utility::string_t& value);
/// <summary>
/// Status is always \&quot;investigating\&quot; — the member of the client&#39;s closed set that means detected, cause not yet established, which is exactly what an automated prober knows. Nothing here ever claims \&quot;identified\&quot;: that would assert a diagnosis no measurement made.
/// </summary>
utility::string_t getStatus() const;
bool statusIsSet() const;
void unsetStatus();
void setStatus(const utility::string_t& value);
/// <summary>
/// URL points at the HUMAN status page, not back at this JSON. Every link in this document goes to the same place.
/// </summary>
utility::string_t getUrl() const;
bool urlIsSet() const;
void unsetUrl();
void setUrl(const utility::string_t& value);
protected:
std::vector<std::shared_ptr<O11y_StatusComponent>> m_Affected_components;
bool m_Affected_componentsIsSet;
utility::string_t m_Current_worst_impact;
bool m_Current_worst_impactIsSet;
utility::string_t m_Id;
bool m_IdIsSet;
utility::string_t m_Last_update_at;
bool m_Last_update_atIsSet;
utility::string_t m_Last_update_message;
bool m_Last_update_messageIsSet;
utility::string_t m_Name;
bool m_NameIsSet;
utility::string_t m_Status;
bool m_StatusIsSet;
utility::string_t m_Url;
bool m_UrlIsSet;
};
}
}
#endif /* HANZO_MODEL_O11y_StatusIncident_H_ */