-
-
Notifications
You must be signed in to change notification settings - Fork 3
Expand file tree
/
Copy pathfile.rs
More file actions
74 lines (60 loc) · 3.3 KB
/
file.rs
File metadata and controls
74 lines (60 loc) · 3.3 KB
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
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
use clap::{Args, ValueHint};
#[derive(Debug, Args)]
#[command(next_help_heading = "File options")]
pub struct CommonFileArgs {
/// Provide one or more additional (custom) demo file(s)
#[arg(short, long = "demo-file", value_name = "DEMO_FILE", value_hint = ValueHint::FilePath, global = true)]
#[arg(long_help = "Provide one or more additional (custom) demo file(s)
Demos are loaded in the following order: Remote (default) demo file, custom
demo files provided via the 'STACKABLE_DEMO_FILES' environment variable, and
lastly demo files provided via the '-d/--demo-file' argument(s). If there are
demos with the same name, the last demo definition will be used.
Use \"stackablectl [OPTIONS] <COMMAND> -d path/to/demos1.yaml -d path/to/demos2.yaml\"
to provide multiple additional demo files.")]
pub demo_files: Vec<String>,
/// Provide one or more additional (custom) stack file(s)
#[arg(short, long = "stack-file", value_name = "STACK_FILE", value_hint = ValueHint::FilePath, global = true)]
#[arg(long_help = "Provide one or more additional (custom) stack file(s)
Stacks are loaded in the following order: Remote (default) stack file, custom
stack files provided via the 'STACKABLE_STACK_FILES' environment variable, and
lastly demo files provided via the '-s/--stack-file' argument(s). If there are
stacks with the same name, the last stack definition will be used.
Use \"stackablectl [OPTIONS] <COMMAND> -s path/to/stacks1.yaml -s path/to/stacks2.yaml\"
to provide multiple additional stack files.")]
pub stack_files: Vec<String>,
/// Provide one or more additional (custom) release file(s)
#[arg(short, long = "release-file", value_name = "RELEASE_FILE", value_hint = ValueHint::FilePath, global = true)]
#[arg(long_help = "Provide one or more additional (custom) release file(s)
Releases are loaded in the following order: Remote (default) release file,
custom release files provided via the 'STACKABLE_RELEASE_FILES' environment
variable, and lastly release files provided via the '-r/--release-file'
argument(s). If there are releases with the same name, the last release
definition will be used.
Use \"stackablectl [OPTIONS] <COMMAND> -r path/to/releases1.yaml -r path/to/releases2.yaml\"
to provide multiple additional release files.")]
pub release_files: Vec<String>,
/// Path to a Helm values file that will be used for the installation of operators
#[arg(short = 'f', long, value_name = "VALUES_FILE", value_hint = ValueHint::FilePath, global = true)]
#[arg(
long_help = "Path to a Helm values file that will be used for the installation of operators
The file is a YAML file containing Helm values used to deploy operators.
Operator-specific keys (e.g. 'airflow-operator', 'zookeeper-operator') map
to the Helm values for that operator. Use YAML anchors and aliases to share
values across operators.
Example values file:
airflow-operator:
tolerations: &default-tolerations
- key: \"example\"
operator: \"Exists\"
effect: \"NoSchedule\"
podAnnotations:
example.com/team: \"data-engineering\"
zookeeper-operator:
tolerations: *default-tolerations
podAnnotations:
example.com/team: \"platform\"
Use \"stackablectl [OPTIONS] <COMMAND> -f path/to/values.yaml\" to provide a
values file."
)]
pub operator_values: Option<String>,
}