You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add linting Git workflow and local linting env (#11)
* Add linter config
* Fix issues raised by linter
* Update sample-appliance.yml
Co-authored-by: Matt Anson <matta@stackhpc.com>
* Update deprecated load_balancer resource
* Fixes needed to run the sample appliance in an Azimuth dev env
Fixed yaml lint issues after running superlint
* Fix issues found by ansible-lint
* Add handlers to load balancer roles
---------
Co-authored-by: Matt Anson <matta@stackhpc.com>
Co-authored-by: Max Norton <maxn@stackhpc.com>
| `cluster_id` | The ID of the cluster. Should be used in the [Terraform state key](./group_vars/openstack.yml#L2). |
102
104
| `cluster_name` | The name of the cluster as given by the user. |
103
105
| `cluster_type` | The name of the cluster type. |
104
106
| `cluster_user_ssh_public_key` | The SSH public key of the user that deployed the cluster. |
105
107
| `cluster_deploy_ssh_public_key` | A cluster-specific SSH public key generated by the CaaS operator. |
106
-
| `cluster_ssh_private_key_file` | The path to a file containing the private key corresponding to `cluster_deploy_ssh_public_key`.<br>This is consumed by the `azimuth_cloud.terraform.infra` role. |
108
+
| `cluster_ssh_private_key_file` | The path to a file containing the private key corresponding to `cluster_deploy_ssh_public_key`.<br>This is consumed by the `azimuth_cloud.terraform.infra` role. |
107
109
| `cluster_network` | The name of the project internal network onto which cluster nodes should be placed. |
108
110
| `cluster_floating_network` | The name of the floating network where floating IPs can be allocated. |
109
111
| `cluster_upgrade_system_packages` | This variable is set when a PATCH operation is requested.<br>If given and `true`, it indicates that system packages should be upgraded. If not given, it should be assumed to be `false`.<br>The mechanism for acheiving this is appliance-specific, but it is expected to be a disruptive operation (e.g. rebuilding nodes).<br>If not given or set to `false`, disruptive operations should be avoided where possible. |
110
112
| `cluster_state` | This variable is set when a DELETE operation is requested.<br>If given and set to `absent` all cluster resources should be deleted, otherwise cluster resources should be updated as normal. |
111
113
114
+
<!-- markdownlint-enable -->
115
+
112
116
## Cluster metadata
113
117
114
118
Each CaaS appliance has a playbook (which may call other playbooks, roles, etc.) and a
@@ -182,3 +186,19 @@ To do this, just use a `debug` task with the variable `outputs` set to a diction
182
186
183
187
For example, this appliance
184
188
[uses the cluster outputs to return the allocated floating IP](./sample-appliance.yml#L29-L34).
189
+
190
+
## Developing locally
191
+
192
+
Locally run the linters that are run in GitHub Actions using:
0 commit comments