You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DATA_SOURCE_NAME='postgresql://postgres:test@localhost:5432/circle_test?sslmode=disable' GOOPTS='-v -tags integration' make test
447
447
```
448
+
449
+
# **Tetrate CVE builds**
450
+
Upstream is not fixing CVEs reported by security scanners, but not applicable to postgres_exporter image.
451
+
These false positives can be fixed by cutting tetrate specific patch releases as follows:
452
+
- Push a commit to a release branch in our fork (e.g. `release-v0.18.1` branch) with the changes to fix the CVEs.
453
+
- Include changes to the `VERSION` file to the new version name following the pattern `<current-version>-tetrate-v<patch-number>`. For example `0.18.1-tetrate-v0` is the first CVEs fixing patch for `0.18.1`.
454
+
- Once the PR is approved and merged:
455
+
- Create the tag and push it to the repository following the pattern `v<new-version>`. For example `v0.18.1-tetrate-v0`.
456
+
- CircleCI will automatically build the images and push them to the [tetrate docker hub repository](https://hub.docker.com/r/tetrate/postgres-exporter).
457
+
- Update tetrate repository to use the new image version.
458
+
Further details for troubleshooting:
459
+
- tag push triggers the `publish_images` custom job in CircleCI that can be found in the `.circleci/config.yml` file.
460
+
- This job uses the [prometheus/publish_release_images](https://circleci.com/developer/orbs/orb/prometheus/publish_release_images) CircleCI orb.
461
+
- CircleCI job details can be found in the [CircleCI dashboard for this project](https://app.circleci.com/projects/github/tetrateio/postgres_exporter).
0 commit comments