Skip to content

Update existing SSH permission requests to match new backend data structures #468

Update existing SSH permission requests to match new backend data structures

Update existing SSH permission requests to match new backend data structures #468

Triggered via pull request November 13, 2024 21:47
Status Failure
Total duration 28s
Artifacts

test.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 1 warning
Test: src/commands/shared/ssh.ts#L93
Element implicitly has an 'any' type because expression of type 'any' can't be used to index type 'Record<"aws" | "azure" | "gcloud", SshProvider<any, any, any, any>>'.
Test: src/commands/shared/ssh.ts#L93
Property 'provider' does not exist on type 'AwsSshPermission | AzureSshPermission | GcpSshPermission'.
Test: src/commands/shared/ssh.ts#L142
Property 'publicKey' does not exist on type 'AwsSshPermission | AzureSshPermission | GcpSshPermission'.
Test: src/commands/shared/ssh.ts#L161
Element implicitly has an 'any' type because expression of type 'any' can't be used to index type 'Record<"aws" | "azure" | "gcloud", SshProvider<any, any, any, any>>'.
Test: src/commands/shared/ssh.ts#L161
Property 'provider' does not exist on type 'AwsSshPermission | AzureSshPermission | GcpSshPermission'.
Test
Process completed with exit code 2.
Test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/