mirror of
https://github.com/hanzo-cpp/sdk.git
synced 2026-11-20 19:55:32 +00:00
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.
77 lines
2.9 KiB
C++
77 lines
2.9 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.
|
|
*/
|
|
|
|
/*
|
|
* SettingsApi.h
|
|
*
|
|
*
|
|
*/
|
|
|
|
#ifndef HANZO_API_SettingsApi_H_
|
|
#define HANZO_API_SettingsApi_H_
|
|
|
|
|
|
|
|
#include "hanzo/ApiClient.h"
|
|
|
|
#include "hanzo/model/SettingsReq.h"
|
|
#include "hanzo/model/SettingsView.h"
|
|
#include <cpprest/details/basic_types.h>
|
|
#include <boost/optional.hpp>
|
|
|
|
namespace hanzo {
|
|
namespace api {
|
|
|
|
using namespace hanzo::model;
|
|
|
|
|
|
|
|
class SettingsApi
|
|
{
|
|
public:
|
|
|
|
explicit SettingsApi( std::shared_ptr<const ApiClient> apiClient );
|
|
|
|
virtual ~SettingsApi();
|
|
|
|
/// <summary>
|
|
/// Reads the caller org's configuration for one product, with every secret field MASKED — only the names of the set secrets come back, never their values, which live in KMS.
|
|
/// </summary>
|
|
/// <remarks>
|
|
/// Reads the caller org's configuration for one product, with every secret field MASKED — only the names of the set secrets come back, never their values, which live in KMS. A product the org has never configured is not a 404: it answers 200 with an empty config object, so the console's Settings tab always renders and merges its own display defaults on top.
|
|
/// </remarks>
|
|
/// <param name="product">Product is the catalog slug, from the path. Must match ^[a-z0-9][a-z0-9._-]{0,62}$.</param>
|
|
pplx::task<std::shared_ptr<SettingsView>> getSettingsByProduct(
|
|
utility::string_t product
|
|
) const;
|
|
/// <summary>
|
|
/// Writes the caller org's configuration for one product and answers the stored result, secrets masked.
|
|
/// </summary>
|
|
/// <remarks>
|
|
/// Writes the caller org's configuration for one product and answers the stored result, secrets masked. Secret VALUES are sealed into KMS under orgs/{org}/settings/{product}/{key} and never touch this deployment's database; with no KMS configured a write that carries any secret is refused whole (503) rather than dropping it or persisting it in the clear. A secret the body omits keeps its stored value, so a partial write never silently clears one.
|
|
/// </remarks>
|
|
/// <param name="product">Product is the catalog slug, from the PATH. zip binds the path last, so the URL names the product being written whatever a body field claims.</param>
|
|
/// <param name="settingsReq"></param>
|
|
pplx::task<std::shared_ptr<SettingsView>> putSettingsByProduct(
|
|
utility::string_t product,
|
|
std::shared_ptr<SettingsReq> settingsReq
|
|
) const;
|
|
|
|
protected:
|
|
std::shared_ptr<const ApiClient> m_ApiClient;
|
|
};
|
|
|
|
}
|
|
}
|
|
|
|
#endif /* HANZO_API_SettingsApi_H_ */
|
|
|