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

130 lines
3.5 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.
*/
/*
* Allowance.h
*
*
*/
#ifndef HANZO_MODEL_Allowance_H_
#define HANZO_MODEL_Allowance_H_
#include <boost/optional.hpp>
#include "hanzo/ModelBase.h"
#include <cpprest/details/basic_types.h>
namespace hanzo {
namespace model {
class Allowance
: public ModelBase
{
public:
Allowance();
virtual ~Allowance();
/////////////////////////////////////////////
/// 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;
/////////////////////////////////////////////
/// Allowance members
/// <summary>
/// calls the plan allows per period; 0 &#x3D; unbounded
/// </summary>
int64_t getLimit() const;
bool limitIsSet() const;
void unsetLimit();
void setLimit(int64_t value);
/// <summary>
/// the tier the limit came from
/// </summary>
utility::string_t getPlan() const;
bool planIsSet() const;
void unsetPlan();
void setPlan(const utility::string_t& value);
/// <summary>
/// unix seconds; when THAT window starts again
/// </summary>
int64_t getResets() const;
bool resetsIsSet() const;
void unsetResets();
void setResets(int64_t value);
/// <summary>
/// the subject is at the limit
/// </summary>
bool isSpent() const;
bool spentIsSet() const;
void unsetSpent();
void setSpent(bool value);
/// <summary>
/// Used is how many zero-priced calls this subject has been SERVED in the period ending at Resets — the UTC calendar day. Only a served call counts, so an admission check, a refusal, or a vendor that never answered leaves it where it stood. It stops AT Limit rather than climbing past it, so Limit-Used is what remains and never goes negative.
/// </summary>
int64_t getUsed() const;
bool usedIsSet() const;
void unsetUsed();
void setUsed(int64_t value);
/// <summary>
/// Window is which ceiling these numbers describe — \&quot;hour\&quot; or \&quot;day\&quot; — because a caller is held to both and only one of them is the answer. It is the window that REFUSED where one did, and otherwise the one with least left, so Limit-Used is always the number that will actually stop them next. Empty where no window bounds the subject at all.
/// </summary>
utility::string_t getWindow() const;
bool windowIsSet() const;
void unsetWindow();
void setWindow(const utility::string_t& value);
protected:
int64_t m_Limit;
bool m_LimitIsSet;
utility::string_t m_Plan;
bool m_PlanIsSet;
int64_t m_Resets;
bool m_ResetsIsSet;
bool m_Spent;
bool m_SpentIsSet;
int64_t m_Used;
bool m_UsedIsSet;
utility::string_t m_Window;
bool m_WindowIsSet;
};
}
}
#endif /* HANZO_MODEL_Allowance_H_ */