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

141 lines
5.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.
*/
/*
* RiskDisposeOut.h
*
*
*/
#ifndef HANZO_MODEL_RiskDisposeOut_H_
#define HANZO_MODEL_RiskDisposeOut_H_
#include <boost/optional.hpp>
#include "hanzo/ModelBase.h"
#include <cpprest/details/basic_types.h>
namespace hanzo {
namespace model {
class RiskDisposeOut
: public ModelBase
{
public:
RiskDisposeOut();
virtual ~RiskDisposeOut();
/////////////////////////////////////////////
/// 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;
/////////////////////////////////////////////
/// RiskDisposeOut members
/// <summary>
/// Before echoes the retention boundary that was applied, RFC 3339 in UTC, as this plane parsed it from the request. What was disposed of is every record WRITTEN strictly before it and not under litigation hold — written, measured against the server clock at the write, and not against the event or observation times the asserting caller supplies, because a tenant that could back-date could delete a compliance record on demand. A boundary younger than the platform floor of five years is refused before anything is removed.
/// </summary>
utility::string_t getBefore() const;
bool beforeIsSet() const;
void unsetBefore();
void setBefore(const utility::string_t& value);
/// <summary>
/// Disposed is how many whole records were removed. Records are disposed of whole, never redacted: a partially-erased compliance record is one nobody can attest to.
/// </summary>
int64_t getDisposed() const;
bool disposedIsSet() const;
void unsetDisposed();
void setDisposed(int64_t value);
/// <summary>
/// Held is how many records inside the boundary were kept under litigation hold.
/// </summary>
int64_t getHeld() const;
bool heldIsSet() const;
void unsetHeld();
void setHeld(int64_t value);
/// <summary>
/// Oldest is the WRITE time of the oldest assertion this tenant still holds after the sweep, RFC 3339, and it is omitted exactly when nothing remains at all. Still older than Before means records survived on purpose and says which mechanism kept them: a litigation hold (Held), or the per-call bound with more to sweep on the next call (Remaining).
/// </summary>
utility::string_t getOldest() const;
bool oldestIsSet() const;
void unsetOldest();
void setOldest(const utility::string_t& value);
/// <summary>
/// Remaining is how many disposable records are still older than the boundary. A sweep is bounded per call, so a non-zero value here means call again rather than that something failed.
/// </summary>
int64_t getRemaining() const;
bool remainingIsSet() const;
void unsetRemaining();
void setRemaining(int64_t value);
/// <summary>
/// Restored is how many records this sweep had already removed from the derived columnar copy and then did NOT dispose of, because a litigation hold arrived between the identify and the delete — and which were therefore written back to the derived copy before this answered. It is a NAMED state and not a silent repair. The copy is swept before the record so nothing is orphaned in the warehouse, which means a record the delete declines to remove is one the warehouse has already lost, with its seq behind the delivery cursor and no retry that can reach it. Non-zero here says the collision happened and was repaired; a non-zero that keeps recurring says retention and hold are racing on the same records, which is worth an operator&#39;s attention rather than a debug line.
/// </summary>
int64_t getRestored() const;
bool restoredIsSet() const;
void unsetRestored();
void setRestored(int64_t value);
/// <summary>
/// Total and Oldest describe what the tenant still holds afterwards, so a disposal that removed nothing is distinguishable from a tenant that had nothing.
/// </summary>
int64_t getTotal() const;
bool totalIsSet() const;
void unsetTotal();
void setTotal(int64_t value);
protected:
utility::string_t m_Before;
bool m_BeforeIsSet;
int64_t m_Disposed;
bool m_DisposedIsSet;
int64_t m_Held;
bool m_HeldIsSet;
utility::string_t m_Oldest;
bool m_OldestIsSet;
int64_t m_Remaining;
bool m_RemainingIsSet;
int64_t m_Restored;
bool m_RestoredIsSet;
int64_t m_Total;
bool m_TotalIsSet;
};
}
}
#endif /* HANZO_MODEL_RiskDisposeOut_H_ */