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

152 lines
5.2 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.
*/
/*
* PatchSessionIn.h
*
*
*/
#ifndef HANZO_MODEL_PatchSessionIn_H_
#define HANZO_MODEL_PatchSessionIn_H_
#include <boost/optional.hpp>
#include "hanzo/ModelBase.h"
#include <cpprest/details/basic_types.h>
namespace hanzo {
namespace model {
class PatchSessionIn
: public ModelBase
{
public:
PatchSessionIn();
virtual ~PatchSessionIn();
/////////////////////////////////////////////
/// 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;
/////////////////////////////////////////////
/// PatchSessionIn members
/// <summary>
/// Cwd is where the session is working NOW. It was write-once — captured at register and never again — which is right for a run that starts in a directory and stays there, and wrong for a linked shell, which is a place a person moves around in. The console showed the directory &#x60;hanzo link&#x60; happened to be run from and kept showing it after the shell had walked away, so the field answered \&quot;which work is this\&quot; with an answer that was true once. A pointer, so an unchanged path is an omitted field rather than a repeated write.
/// </summary>
utility::string_t getCwd() const;
bool cwdIsSet() const;
void unsetCwd();
void setCwd(const utility::string_t& value);
/// <summary>
/// ID is the session to update, from the path.
/// </summary>
utility::string_t getId() const;
bool idIsSet() const;
void unsetId();
void setId(const utility::string_t& value);
/// <summary>
/// Project tags the product this session built; Published is the author&#39;s decision to let anyone read the story (provenance.go). Both are pointers so \&quot;absent\&quot; and \&quot;cleared\&quot; are different requests.
/// </summary>
utility::string_t getProject() const;
bool projectIsSet() const;
void unsetProject();
void setProject(const utility::string_t& value);
/// <summary>
/// Published opens the session&#39;s story to the public build route; false withdraws it, and withdrawing is always allowed. PUBLISHING is refused unless the session names a Project — the one set in this same request, or the one already stored — because that route is keyed on (org, project). It widens READ access to what is already there and grants nothing else.
/// </summary>
bool isPublished() const;
bool publishedIsSet() const;
void unsetPublished();
void setPublished(bool value);
/// <summary>
/// Status moves the session to running, paused, done or error. A session that has already finished refuses any change with 409 — done and error are monotonic — and moving INTO one stamps the end time. This is the surface REPORTING what happened; a control command never writes it.
/// </summary>
utility::string_t getStatus() const;
bool statusIsSet() const;
void unsetStatus();
void setStatus(const utility::string_t& value);
/// <summary>
/// Target re-dispatches a session to a run-target (the #48 association). \&quot;\&quot; detaches.
/// </summary>
utility::string_t getTarget() const;
bool targetIsSet() const;
void unsetTarget();
void setTarget(const utility::string_t& value);
/// <summary>
/// Terminal publishes (or, with \&quot;\&quot;, withdraws) the URL this session&#39;s live terminal can be watched at. A pointer so \&quot;absent\&quot; and \&quot;withdrawn\&quot; are different requests: a session that stops sharing must be able to say so.
/// </summary>
utility::string_t getTerminal() const;
bool terminalIsSet() const;
void unsetTerminal();
void setTerminal(const utility::string_t& value);
/// <summary>
/// Title rewrites the human line, up to 512 characters — usually because the work turned out to be something other than what it was opened as.
/// </summary>
utility::string_t getTitle() const;
bool titleIsSet() const;
void unsetTitle();
void setTitle(const utility::string_t& value);
protected:
utility::string_t m_Cwd;
bool m_CwdIsSet;
utility::string_t m_Id;
bool m_IdIsSet;
utility::string_t m_Project;
bool m_ProjectIsSet;
bool m_Published;
bool m_PublishedIsSet;
utility::string_t m_Status;
bool m_StatusIsSet;
utility::string_t m_Target;
bool m_TargetIsSet;
utility::string_t m_Terminal;
bool m_TerminalIsSet;
utility::string_t m_Title;
bool m_TitleIsSet;
};
}
}
#endif /* HANZO_MODEL_PatchSessionIn_H_ */