Skip to content

Fix viper config unmarshalling #256

Fix viper config unmarshalling

Fix viper config unmarshalling #256

Triggered via pull request August 2, 2023 22:09
Status Success
Total duration 3m 54s
Artifacts

tests.yaml

on: pull_request
Dependencies
21s
Dependencies
Unit Test
2m 10s
Unit Test
Nats Test End to End
3m 8s
Nats Test End to End
GRPC Test End to End
3m 16s
GRPC Test End to End
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Dependencies
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v1, actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Unit Test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v1, actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Nats Test End to End
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v1, actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
GRPC Test End to End
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v1, actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/