Files
zeekay 189ce08e51 Regenerate against the document the deployment answers for
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.
2026-09-05 18:07:13 -07:00

108 lines
2.7 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.
*/
/*
* PresignResponse.h
*
*
*/
#ifndef HANZO_MODEL_PresignResponse_H_
#define HANZO_MODEL_PresignResponse_H_
#include <boost/optional.hpp>
#include "hanzo/ModelBase.h"
#include <cpprest/details/basic_types.h>
namespace hanzo {
namespace model {
class PresignResponse
: public ModelBase
{
public:
PresignResponse();
virtual ~PresignResponse();
/////////////////////////////////////////////
/// 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;
/////////////////////////////////////////////
/// PresignResponse members
/// <summary>
/// seconds until the URL expires
/// </summary>
int64_t getExpiresIn() const;
bool expiresInIsSet() const;
void unsetExpiresIn();
void setExpiresIn(int64_t value);
/// <summary>
/// Key is the object key the URL was signed for, relative to the bucket root and path-cleaned — so it is what the store will actually read or write, which is not always the string the caller sent. The signature covers this one bucket and this one key: a URL minted here reaches nothing else.
/// </summary>
utility::string_t getKey() const;
bool keyIsSet() const;
void unsetKey();
void setKey(const utility::string_t& value);
/// <summary>
/// \&quot;PUT\&quot; (upload) or \&quot;GET\&quot; (download)
/// </summary>
utility::string_t getMethod() const;
bool methodIsSet() const;
void unsetMethod();
void setMethod(const utility::string_t& value);
/// <summary>
/// presigned URL the browser follows directly
/// </summary>
utility::string_t getUrl() const;
bool urlIsSet() const;
void unsetUrl();
void setUrl(const utility::string_t& value);
protected:
int64_t m_ExpiresIn;
bool m_ExpiresInIsSet;
utility::string_t m_Key;
bool m_KeyIsSet;
utility::string_t m_Method;
bool m_MethodIsSet;
utility::string_t m_Url;
bool m_UrlIsSet;
};
}
}
#endif /* HANZO_MODEL_PresignResponse_H_ */