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

76 lines
2.4 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.
*/
/*
* PubsubApi.h
*
*
*/
#ifndef HANZO_API_PubsubApi_H_
#define HANZO_API_PubsubApi_H_
#include "hanzo/ApiClient.h"
#include "hanzo/model/BusAck.h"
#include "hanzo/model/BusMessage.h"
#include "hanzo/model/BusPublish.h"
#include "hanzo/model/BusRequest.h"
#include <boost/optional.hpp>
namespace hanzo {
namespace api {
using namespace hanzo::model;
class PubsubApi
{
public:
explicit PubsubApi( std::shared_ptr<const ApiClient> apiClient );
virtual ~PubsubApi();
/// <summary>
/// Publish puts one message on the org&#39;s bus.
/// </summary>
/// <remarks>
/// Publish puts one message on the org&#39;s bus. When a stream captures the subject the write is DURABLE — the receipt names the stream and sequence only after JetStream has it on storage, and a repeated Nats-Msg-Id header within the dedup window answers duplicate instead of storing twice. When nothing captures it, the message goes out core NATS: delivered to current subscribers, receipt {ok}, nothing retained.
/// </remarks>
/// <param name="busPublish"></param>
pplx::task<std::shared_ptr<BusAck>> postPubsubPublish(
std::shared_ptr<BusPublish> busPublish
) const;
/// <summary>
/// Request sends one request on the org&#39;s bus and waits for one reply — the synchronous half of pub/sub, for callers speaking to a responder subscribed on the NATS port.
/// </summary>
/// <remarks>
/// Request sends one request on the org&#39;s bus and waits for one reply — the synchronous half of pub/sub, for callers speaking to a responder subscribed on the NATS port. 404 when nobody is listening on the subject; 408 when a responder exists but no reply arrived within the timeout.
/// </remarks>
/// <param name="busRequest"></param>
pplx::task<std::shared_ptr<BusMessage>> postPubsubRequest(
std::shared_ptr<BusRequest> busRequest
) const;
protected:
std::shared_ptr<const ApiClient> m_ApiClient;
};
}
}
#endif /* HANZO_API_PubsubApi_H_ */