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.
97 lines
2.6 KiB
C++
97 lines
2.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.
|
|
*/
|
|
|
|
/*
|
|
* ReferenceOverrideIn.h
|
|
*
|
|
*
|
|
*/
|
|
|
|
#ifndef HANZO_MODEL_ReferenceOverrideIn_H_
|
|
#define HANZO_MODEL_ReferenceOverrideIn_H_
|
|
|
|
#include <boost/optional.hpp>
|
|
|
|
#include "hanzo/ModelBase.h"
|
|
|
|
#include <cpprest/details/basic_types.h>
|
|
|
|
namespace hanzo {
|
|
namespace model {
|
|
|
|
|
|
|
|
class ReferenceOverrideIn
|
|
: public ModelBase
|
|
{
|
|
public:
|
|
ReferenceOverrideIn();
|
|
virtual ~ReferenceOverrideIn();
|
|
|
|
/////////////////////////////////////////////
|
|
/// 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;
|
|
|
|
|
|
/////////////////////////////////////////////
|
|
/// ReferenceOverrideIn members
|
|
|
|
|
|
/// <summary>
|
|
/// Key is the member: a domain, a CIDR or address, an issuer prefix, a device digest. It is matched the same way the baseline is, so a deny on tempbox.example also covers mail.tempbox.example.
|
|
/// </summary>
|
|
utility::string_t getKey() const;
|
|
bool keyIsSet() const;
|
|
void unsetKey();
|
|
void setKey(const utility::string_t& value);
|
|
|
|
/// <summary>
|
|
/// Note is why, in your own words. Optional, bounded to 512 bytes.
|
|
/// </summary>
|
|
utility::string_t getNote() const;
|
|
bool noteIsSet() const;
|
|
void unsetNote();
|
|
void setNote(const utility::string_t& value);
|
|
|
|
/// <summary>
|
|
/// Verdict is allow or deny, and nothing else. An override is a decision — unlike a baseline entry, which states facts and leaves the decision to your policy — because your organisation is the only party entitled to say \"for us, this one is fine\".
|
|
/// </summary>
|
|
utility::string_t getVerdict() const;
|
|
bool verdictIsSet() const;
|
|
void unsetVerdict();
|
|
void setVerdict(const utility::string_t& value);
|
|
|
|
|
|
protected:
|
|
utility::string_t m_Key;
|
|
bool m_KeyIsSet;
|
|
|
|
utility::string_t m_Note;
|
|
bool m_NoteIsSet;
|
|
|
|
utility::string_t m_Verdict;
|
|
bool m_VerdictIsSet;
|
|
|
|
};
|
|
|
|
|
|
}
|
|
}
|
|
|
|
#endif /* HANZO_MODEL_ReferenceOverrideIn_H_ */
|