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

158 lines
5.2 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.
*/
/*
* HealthReport.h
*
*
*/
#ifndef HANZO_MODEL_HealthReport_H_
#define HANZO_MODEL_HealthReport_H_
#include <boost/optional.hpp>
#include "hanzo/ModelBase.h"
#include <cpprest/details/basic_types.h>
#include "hanzo/model/HealthLenses.h"
#include "hanzo/model/HealthPlane.h"
#include "hanzo/model/Loss.h"
namespace hanzo {
namespace model {
class HealthLenses;
class Loss;
class HealthPlane;
class HealthReport
: public ModelBase
{
public:
HealthReport();
virtual ~HealthReport();
/////////////////////////////////////////////
/// 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;
/////////////////////////////////////////////
/// HealthReport members
/// <summary>
/// Datastore reports whether the shared warehouse client has a live connection. It is load-bearing for the READ path: false is one of the two ways this answers 503.
/// </summary>
bool isDatastore() const;
bool datastoreIsSet() const;
void unsetDatastore();
void setDatastore(bool value);
/// <summary>
/// Lenses is per-lens table availability, probed only when connected — so it is absent from a degraded report, which has nothing to say about tables it could not reach.
/// </summary>
std::shared_ptr<HealthLenses> getLenses() const;
bool lensesIsSet() const;
void unsetLenses();
void setLenses(const std::shared_ptr<HealthLenses>& value);
/// <summary>
/// Lost is the count of facts the sink irrecoverably dropped since boot (warehouse.go). It is reported on the DEGRADED report too, and deliberately: a warehouse that is unreachable is exactly when facts start failing their deliveries, so suppressing the number here would hide it precisely when it moves. ANY NON-ZERO VALUE IS AN ALARM — it counts data the endpoint already answered 200 for.
/// </summary>
std::shared_ptr<Loss> getLost() const;
bool lostIsSet() const;
void unsetLost();
void setLost(const std::shared_ptr<Loss>& value);
/// <summary>
/// Plane reports the event plane — the bus and the stream every accepted event is published to BEFORE any of it reaches the warehouse. It is load-bearing for the WRITE path, and it is here because its absence was a real outage: this endpoint answered 200/ok on warehouse connectivity alone while every POST /v1/event 503&#39;d on a stream that could not bind, so 100% ingest loss was invisible to monitoring. A probe that cannot see the write path cannot report the write path.
/// </summary>
std::shared_ptr<HealthPlane> getPlane() const;
bool planeIsSet() const;
void unsetPlane();
void setPlane(const std::shared_ptr<HealthPlane>& value);
/// <summary>
/// Reason is the human-readable cause, present only on a degraded report.
/// </summary>
utility::string_t getReason() const;
bool reasonIsSet() const;
void unsetReason();
void setReason(const utility::string_t& value);
/// <summary>
/// Service names the subsystem answering, so a probe aggregating several health endpoints can attribute a degraded one.
/// </summary>
utility::string_t getService() const;
bool serviceIsSet() const;
void unsetService();
void setService(const utility::string_t& value);
/// <summary>
/// Status is ok or degraded. Degraded is the 503 and means EITHER load-bearing dependency is down — the warehouse this subsystem reads, or the event plane it writes. It is not moved by a missing lens table, which is honest-empty.
/// </summary>
utility::string_t getStatus() const;
bool statusIsSet() const;
void unsetStatus();
void setStatus(const utility::string_t& value);
/// <summary>
/// Warehouse names the datastore database every lens reads.
/// </summary>
utility::string_t getWarehouse() const;
bool warehouseIsSet() const;
void unsetWarehouse();
void setWarehouse(const utility::string_t& value);
protected:
bool m_Datastore;
bool m_DatastoreIsSet;
std::shared_ptr<HealthLenses> m_Lenses;
bool m_LensesIsSet;
std::shared_ptr<Loss> m_Lost;
bool m_LostIsSet;
std::shared_ptr<HealthPlane> m_Plane;
bool m_PlaneIsSet;
utility::string_t m_Reason;
bool m_ReasonIsSet;
utility::string_t m_Service;
bool m_ServiceIsSet;
utility::string_t m_Status;
bool m_StatusIsSet;
utility::string_t m_Warehouse;
bool m_WarehouseIsSet;
};
}
}
#endif /* HANZO_MODEL_HealthReport_H_ */