mirror of
https://github.com/hanzo-cpp/sdk.git
synced 2026-11-20 19:55:32 +00:00
The projection these were generated from was a month old and predated the compute migration, so every one of them described /v1/visor — which the API serves at zero paths now. That is why a hand-written console client and a generated one had drifted the same way at the same time. No /v1/visor path survives here. The word still appears as a source-plane value and inside gvisor and supervisor, which are not this rename.
86 lines
2.1 KiB
C++
86 lines
2.1 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.
|
|
*/
|
|
|
|
/*
|
|
* ApprovePairingIn.h
|
|
*
|
|
*
|
|
*/
|
|
|
|
#ifndef HANZO_MODEL_ApprovePairingIn_H_
|
|
#define HANZO_MODEL_ApprovePairingIn_H_
|
|
|
|
#include <boost/optional.hpp>
|
|
|
|
#include "hanzo/ModelBase.h"
|
|
|
|
#include <cpprest/details/basic_types.h>
|
|
|
|
namespace hanzo {
|
|
namespace model {
|
|
|
|
|
|
|
|
class ApprovePairingIn
|
|
: public ModelBase
|
|
{
|
|
public:
|
|
ApprovePairingIn();
|
|
virtual ~ApprovePairingIn();
|
|
|
|
/////////////////////////////////////////////
|
|
/// 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;
|
|
|
|
|
|
/////////////////////////////////////////////
|
|
/// ApprovePairingIn members
|
|
|
|
|
|
/// <summary>
|
|
/// Channel is the transport the request came in on: discord, slack, teams, telegram or whatsapp.
|
|
/// </summary>
|
|
utility::string_t getChannel() const;
|
|
bool channelIsSet() const;
|
|
void unsetChannel();
|
|
void setChannel(const utility::string_t& value);
|
|
|
|
/// <summary>
|
|
/// Code is the pairing code from GET /v1/channel/pairing. It is a capability: holding it is what authorises the approval, alongside org admin.
|
|
/// </summary>
|
|
utility::string_t getCode() const;
|
|
bool codeIsSet() const;
|
|
void unsetCode();
|
|
void setCode(const utility::string_t& value);
|
|
|
|
|
|
protected:
|
|
utility::string_t m_Channel;
|
|
bool m_ChannelIsSet;
|
|
|
|
utility::string_t m_Code;
|
|
bool m_CodeIsSet;
|
|
|
|
};
|
|
|
|
|
|
}
|
|
}
|
|
|
|
#endif /* HANZO_MODEL_ApprovePairingIn_H_ */
|