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

112 lines
4.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.
*/
/*
* PublishResult.h
*
*
*/
#ifndef HANZO_MODEL_PublishResult_H_
#define HANZO_MODEL_PublishResult_H_
#include <boost/optional.hpp>
#include "hanzo/ModelBase.h"
#include "hanzo/model/ChannelResult.h"
#include <cpprest/details/basic_types.h>
#include <map>
#include <vector>
namespace hanzo {
namespace model {
class ChannelResult;
class PublishResult
: public ModelBase
{
public:
PublishResult();
virtual ~PublishResult();
/////////////////////////////////////////////
/// 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;
/////////////////////////////////////////////
/// PublishResult members
/// <summary>
/// Channels is the channel list read off the content document — integration ids or provider names, as the item declares them. Empty when the item names none, which targets every connected, enabled channel. It is what was ASKED for; Results is what happened.
/// </summary>
std::vector<utility::string_t> getChannels() const;
bool channelsIsSet() const;
void unsetChannels();
void setChannels(const std::vector<utility::string_t>& value);
/// <summary>
/// ExternalIDs maps channel id → the post id that channel returned, merged with everything earlier publishes recorded. Successes only, and it is the idempotency ledger: a channel named here is skipped by every later publish of this item, so the map only ever grows.
/// </summary>
std::map<utility::string_t, utility::string_t> getExternalIds() const;
bool externalIdsIsSet() const;
void unsetExternalIds();
void setExternalIds(const std::map<utility::string_t, utility::string_t>& value);
/// <summary>
/// Results is the outcome per channel — which went out, which did not and why — covering the whole fan-out including failures, so partial success is never flattened into one verdict. A channel the org has not connected appears here as failed with \&quot;channel not connected\&quot;.
/// </summary>
std::vector<std::shared_ptr<ChannelResult>> getResults() const;
bool resultsIsSet() const;
void unsetResults();
void setResults(const std::vector<std::shared_ptr<ChannelResult>>& value);
/// <summary>
/// Status is the ONE headline, drawn from: \&quot;distributed\&quot; (something is on record and went out now), \&quot;scheduled\&quot; (same, handed to the channel&#39;s own scheduler for later), \&quot;failed\&quot; (nothing is on record — this fan-out missed entirely and no earlier one landed), \&quot;in_progress\&quot; (another publisher holds the item, so this call posted NOTHING and the caller retries), and \&quot;not_configured\&quot; (no distribution edge is wired; a transition records it instead of failing). A partial fan-out is \&quot;distributed\&quot;/\&quot;scheduled\&quot;, never \&quot;failed\&quot; — the per-channel truth is in Results.
/// </summary>
utility::string_t getStatus() const;
bool statusIsSet() const;
void unsetStatus();
void setStatus(const utility::string_t& value);
protected:
std::vector<utility::string_t> m_Channels;
bool m_ChannelsIsSet;
std::map<utility::string_t, utility::string_t> m_ExternalIds;
bool m_ExternalIdsIsSet;
std::vector<std::shared_ptr<ChannelResult>> m_Results;
bool m_ResultsIsSet;
utility::string_t m_Status;
bool m_StatusIsSet;
};
}
}
#endif /* HANZO_MODEL_PublishResult_H_ */