Skip to content

encrypt *LB access logs if KMS key is specified #145

encrypt *LB access logs if KMS key is specified

encrypt *LB access logs if KMS key is specified #145

Triggered via pull request February 12, 2024 22:09
Status Failure
Total duration 2m 2s
Artifacts

lint.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 11 warnings
lint: state/s3.yaml#L220
220:17 syntax error: expected <block end>, but found '<block sequence start>' (syntax)
lint: state/s3.yaml#L222
222:17 [indentation] wrong indentation: expected 18 but found 16
lint
Process completed with exit code 1.
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