1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
/*
* 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
*
* Generated by: https://openapi-generator.tech
*/
use crate::models;
use serde::{Deserialize, Serialize};
#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
pub struct StrategyView {
/// Action is the tactic itself: the thing to go and do.
#[serde(rename = "action", skip_serializing_if = "Option::is_none")]
pub action: Option<String>,
/// Category is the growth discipline the tactic belongs to — the axis `?category=` narrows on.
#[serde(rename = "category", skip_serializing_if = "Option::is_none")]
pub category: Option<String>,
/// ID is the tactic's stable slug in the corpus.
#[serde(rename = "id", skip_serializing_if = "Option::is_none")]
pub id: Option<String>,
/// Tags are the PRECONDITIONS this tactic already satisfied to appear in the answer — `stage:<name>` and `has:<capability>` predicates over the org's observed profile. They are carried back so a caller can show why a tactic surfaced, not so it can filter again.
#[serde(rename = "tags", skip_serializing_if = "Option::is_none")]
pub tags: Option<Vec<String>>,
/// Workload is how much effort running the tactic costs, so a corpus can be cut to what the org has the hands for.
#[serde(rename = "workload", skip_serializing_if = "Option::is_none")]
pub workload: Option<String>,
}
impl StrategyView {
pub fn new() -> StrategyView {
StrategyView {
action: None,
category: None,
id: None,
tags: None,
workload: None,
}
}
}