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

97 lines
2.8 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.
*/
/*
* ConnectIn.h
*
*
*/
#ifndef HANZO_MODEL_ConnectIn_H_
#define HANZO_MODEL_ConnectIn_H_
#include <boost/optional.hpp>
#include "hanzo/ModelBase.h"
#include <cpprest/details/basic_types.h>
namespace hanzo {
namespace model {
class ConnectIn
: public ModelBase
{
public:
ConnectIn();
virtual ~ConnectIn();
/////////////////////////////////////////////
/// 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;
/////////////////////////////////////////////
/// ConnectIn members
/// <summary>
/// AccountID is the provider account the credential should be scoped to, for the providers whose Verify needs one (Cloudflare). Ignored by the OAuth path.
/// </summary>
utility::string_t getAccountId() const;
bool accountIdIsSet() const;
void unsetAccountId();
void setAccountId(const utility::string_t& value);
/// <summary>
/// Provider is the connector&#39;s registry id, from the :provider path segment.
/// </summary>
utility::string_t getProvider() const;
bool providerIsSet() const;
void unsetProvider();
void setProvider(const utility::string_t& value);
/// <summary>
/// Token is the customer&#39;s provider credential. Its PRESENCE — not its value — is what selects the apikey seal over the OAuth flow for a provider that offers both: {\&quot;token\&quot;:\&quot;…\&quot;}, even empty, is an apikey attempt (→ verify, which answers the \&quot;token required\&quot; 400 on an empty value), while a body with no token key (the console Connect button, &#x60;hanzo connector add&#x60; with no --token) starts OAuth. Read on STDIN by the CLI, never argv; never logged or echoed.
/// </summary>
utility::string_t getToken() const;
bool tokenIsSet() const;
void unsetToken();
void setToken(const utility::string_t& value);
protected:
utility::string_t m_AccountId;
bool m_AccountIdIsSet;
utility::string_t m_Provider;
bool m_ProviderIsSet;
utility::string_t m_Token;
bool m_TokenIsSet;
};
}
}
#endif /* HANZO_MODEL_ConnectIn_H_ */