Skip to content

docs(vector): document services.vector updates with VECTOR_VERSION #152

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
catinspace-au merged 1 commit into from
Nov 11, 2026
Merged

docs(vector): document services.vector updates with VECTOR_VERSION #152

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/architecture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ API, which the supervisor does not do.

## Build, chart and licence invariants

**The Vector version has one source.** The constant `VECTOR_VERSION` in `src/deployment.rs` is substituted into the Dockerfile's `ARG VECTOR_VERSION`, and both `VectorConfig::default()` and the contract's `default_config` read it for `vector.version`. `version_check: strict` refuses to start a pod when the config's version and the binary's disagree, so a deployment that sets `vector.version` itself has to move it with the image.
**The Vector version has one source.** The constant `VECTOR_VERSION` in `src/deployment.rs` is substituted into the Dockerfile's `ARG VECTOR_VERSION`, and both `VectorConfig::default()` and the contract's `default_config` read it for `vector.version`. `version_check: strict` refuses to start a pod when the config's version and the binary's disagree, so a deployment that sets `vector.version` itself has to move it with the image. dfe-infra's `versions.yaml` records the same release as `services.vector`, and dfe-fetcher's container Vector extractor runs that image.

**`password` is a `String` on purpose, not a `SensitiveString`.** The config
goes through a figment serialize-merge-deserialize round trip in
Expand Down
3 changes: 3 additions & 0 deletions docs/internals.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -634,6 +634,9 @@ ENTRYPOINT ["dfe-transform-vector"]
pin. Do NOT edit the Dockerfile: it is autogenerated, and
`checked_in_dockerfile_matches_emit_dockerfile` fails if it drifts.
2. Regenerate: `cargo run -- emit-dockerfile > Dockerfile`
Then move `services.vector` in dfe-infra's `versions.yaml` to the same
release (its tag is `<version>-alpine`). dfe-fetcher's container Vector
extractor runs that image, so the two must name one release.
3. Rebuild image — only the vector and runtime stages rebuild (layer cache)
4. CI runs integration tests against the new Vector version
5. Deploy
Expand Down
Loading