encrypt *LB access logs if KMS key is specified #141
ab77Annotations
10 errors and 11 warnings
|
lint:
state/s3.yaml#L220
220:17 syntax error: expected the node content, but found '-' (syntax)
|
|
lint:
state/s3.yaml#L222
222:17 [indentation] wrong indentation: expected 18 but found 16
|
|
lint:
state/s3.yaml#L222
222:65 [indentation] cannot infer indentation: unexpected token
|
|
lint:
state/s3.yaml#L223
223:11 [indentation] wrong indentation: expected 18 but found 10
|
|
lint:
state/s3.yaml#L224
224:9 [indentation] wrong indentation: expected 10 but found 8
|
|
lint:
state/s3.yaml#L226
226:22 [indentation] cannot infer indentation: unexpected token
|
|
lint:
state/s3.yaml#L227
227:13 [indentation] wrong indentation: expected 18 but found 12
|
|
lint:
state/s3.yaml#L227
227:19 [indentation] cannot infer indentation: unexpected token
|
|
lint:
state/s3.yaml#L228
228:13 [indentation] wrong indentation: expected 18 but found 12
|
|
lint:
state/s3.yaml#L228
228:19 [indentation] cannot infer indentation: unexpected token
|
|
lint
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.312.0. Please update to the latest version 2.313.0
|
|
lint:
.readthedocs.yaml#L4
4:1 [document-start] missing document start "---"
|
|
lint:
vpc/vpc-3azs.yaml#L67
67:8 [comments] missing starting space in comment
|
|
lint:
vpc/vpc-3azs.yaml#L96
96:8 [comments] missing starting space in comment
|
|
lint:
vpc/vpc-3azs.yaml#L125
125:8 [comments] missing starting space in comment
|
|
lint:
vpc/vpc-4azs.yaml#L67
67:8 [comments] missing starting space in comment
|
|
lint:
vpc/vpc-4azs.yaml#L96
96:8 [comments] missing starting space in comment
|
|
lint:
vpc/vpc-4azs.yaml#L125
125:8 [comments] missing starting space in comment
|
|
lint:
vpc/vpc-4azs.yaml#L154
154:8 [comments] missing starting space in comment
|
|
lint:
vpc/vpc-2azs.yaml#L67
67:8 [comments] missing starting space in comment
|
|
lint:
vpc/vpc-2azs.yaml#L96
96:8 [comments] missing starting space in comment
|