Skip to content
This repository has been archived by the owner on Jan 29, 2024. It is now read-only.

How to access Aiven services from Google Cloud Functions via VPC peering #2993

How to access Aiven services from Google Cloud Functions via VPC peering

How to access Aiven services from Google Cloud Functions via VPC peering #2993

Triggered via pull request January 29, 2024 08:03
Status Success
Total duration 7m 59s
Artifacts

build.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
[vale] docs/platform/howto/google-cloud-functions.rst#L1: docs/platform/howto/google-cloud-functions.rst#L1
[Aiven.capitalization_headings] 'How to access Aiven services from Google Cloud Functions via VPC peering' should be in sentence case
[vale] docs/platform/howto/google-cloud-functions.rst#L14: docs/platform/howto/google-cloud-functions.rst#L14
[Aiven.capitalization_headings] 'First, create Serverless VPC access connector' should be in sentence case
[vale] docs/platform/howto/google-cloud-functions.rst#L27: docs/platform/howto/google-cloud-functions.rst#L27
[Aiven.capitalization_headings] 'Create Cloud Function' should be in sentence case
run-checks
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-python@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
run-checks
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/