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

100 lines
3.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.
*/
/*
* ProfileResponse.h
*
*
*/
#ifndef HANZO_MODEL_ProfileResponse_H_
#define HANZO_MODEL_ProfileResponse_H_
#include <boost/optional.hpp>
#include "hanzo/ModelBase.h"
#include <cpprest/details/basic_types.h>
#include "hanzo/model/ProfileMetrics.h"
#include <map>
namespace hanzo {
namespace model {
class ProfileMetrics;
class ProfileResponse
: public ModelBase
{
public:
ProfileResponse();
virtual ~ProfileResponse();
/////////////////////////////////////////////
/// 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;
/////////////////////////////////////////////
/// ProfileResponse members
/// <summary>
/// KeyMetrics are the org&#39;s OWN numbers behind those signals — never another org&#39;s, and never a platform aggregate.
/// </summary>
std::shared_ptr<ProfileMetrics> getKeyMetrics() const;
bool keyMetricsIsSet() const;
void unsetKeyMetrics();
void setKeyMetrics(const std::shared_ptr<ProfileMetrics>& value);
/// <summary>
/// Signals is what was observed of the org right now, one boolean per probe. A probe that could not be run reports FALSE, not absent — the shape is stable so a caller never has to tell a missing key from a negative answer, and the cost is that \&quot;not observed\&quot; and \&quot;not there\&quot; look alike here. Keys are the probe names, including the &#x60;module:&lt;name&gt;&#x60; and &#x60;connected:&lt;provider&gt;&#x60; families.
/// </summary>
std::map<utility::string_t, bool> getSignals() const;
bool signalsIsSet() const;
void unsetSignals();
void setSignals(std::map<utility::string_t, bool> value);
/// <summary>
/// Stage is how far the business itself has got — formed, launched, activated or scaling — decided purely from the signals below, and by what the org has ACHIEVED rather than what it has configured. It reads the STRONGEST evidence present, so money of record makes an org scaling even if an earlier rung&#39;s signal was never observed. It is unrelated to checklist progress.
/// </summary>
utility::string_t getStage() const;
bool stageIsSet() const;
void unsetStage();
void setStage(const utility::string_t& value);
protected:
std::shared_ptr<ProfileMetrics> m_KeyMetrics;
bool m_KeyMetricsIsSet;
std::map<utility::string_t, bool> m_Signals;
bool m_SignalsIsSet;
utility::string_t m_Stage;
bool m_StageIsSet;
};
}
}
#endif /* HANZO_MODEL_ProfileResponse_H_ */