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.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.
*/
/*
* AuthzApi.h
*
*
*/
#ifndef HANZO_API_AuthzApi_H_
#define HANZO_API_AuthzApi_H_
#include "hanzo/ApiClient.h"
#include "hanzo/ModelBase.h"
#include <boost/optional.hpp>
namespace hanzo {
namespace api {
using namespace hanzo::model;
class AuthzApi
{
public:
explicit AuthzApi( std::shared_ptr<const ApiClient> apiClient );
virtual ~AuthzApi();
/// <summary>
/// Liveness of the policy engine
/// </summary>
/// <remarks>
/// Reports that the authz process is up. Unauthenticated by design and never org-scoped: it answers while every tenant&#39;s enforcer is still cold, because a probe that needed a tenant would fail for reasons that have nothing to do with the process being alive.
/// </remarks>
pplx::task<void> getAuthzHealth(
) const;
/// <summary>
/// Readiness of the policy engine
/// </summary>
/// <remarks>
/// Reports that the authz process is ready to serve decisions. Unauthenticated and not org-scoped, for the same reason health is: readiness is a property of this process, not of any one tenant&#39;s policy set.
/// </remarks>
pplx::task<void> getAuthzReadyz(
) const;
/// <summary>
/// Ask whether a subject may act on an object
/// </summary>
/// <remarks>
/// Answers one policy question — may this subject take this action on this object — against the CALLER&#39;S OWN org policy set, and answers it with a bare allow/deny. The org comes from the gateway-minted X-Org-Id and picks the per-org enforcer, so a decision is always rendered by that tenant&#39;s policies and never by another&#39;s. A request carrying no org is refused rather than answered from a shared or default set: collapsing tenants together is the one failure a policy engine must not have. Body: {sub, obj, act}, all three required. The reply echoes them beside &#x60;allow&#x60; so a cached or logged decision carries the question it answered.
/// </remarks>
pplx::task<void> postAuthzCheck(
) const;
protected:
std::shared_ptr<const ApiClient> m_ApiClient;
};
}
}
#endif /* HANZO_API_AuthzApi_H_ */