feat: add vectordotdev/vector

[kquinsland]

Summary

Add vectordotdev/vector to aqua-registry.

Vector publishes multiple release families from the same repository, so this package excludes vdev-* releases; they appear to be maintenance/internal things.

I targeted the main v0.x Vector release line.
I gave Codex github API access and asked it to build a through line of versions to confirm the various version_overrides notes.
I can make the argument for not including the older versions since: a) they're old and b) it wasn't until release v0.33.1 that sha256 checksums were published, so the older versions are less secure to use.

I included them for completeness and because they still work.
I can remove them if "newer, more secure" is preferred over "more complete, but older and less secure".

Verification

Generated with:

aqua gr --init vectordotdev/vector
argd s -B --local -c aqua-generate-registry.yaml vectordotdev/vector
argd gr

Tested with:

❯ conftest test pkgs/vectordotdev/vector/*.yaml

28 tests, 28 passed, 0 warnings, 0 failures, 0 exceptions

❯ argd t vectordotdev/vector
May  9 15:10:14.979 INF checking if the container exists program=argd version=0.5.2 container_name=aqua-registry
May  9 15:10:14.989 INF checking if the container is running program=argd version=0.5.2 container_name=aqua-registry
May  9 15:10:15.018 INF Dockerfile isn't updated program=argd version=0.5.2
# <...>
Successfully copied 403B (transferred 2.05kB) to aqua-registry-windows:/workspace/pkg.yaml
May  9 15:10:15.450 INF + /usr/bin/docker cp pkgs/vectordotdev/vector/registry.yaml aqua-registry-windows:/workspace/registry.yaml program=argd version=0.5.2
Successfully copied 7.71kB (transferred 9.73kB) to aqua-registry-windows:/workspace/registry.yaml
May  9 15:10:15.463 INF testing program=argd version=0.5.2 os=windows arch=amd64
May  9 15:10:15.463 INF + /usr/bin/docker exec -w /workspace aqua-registry-windows bash -c rm aqua-checksums.json 2>/dev/null || : program=argd version=0.5.2
May  9 15:10:15.498 INF + /usr/bin/docker exec -w /workspace -e AQUA_GOOS=windows -e AQUA_GOARCH=amd64 -e AQUA_GITHUB_TOKEN= aqua-registry-windows aqua i program=argd version=0.5.2
May  9 15:10:15.548 INF testing program=argd version=0.5.2 os=windows arch=arm64
May  9 15:10:15.548 INF + /usr/bin/docker exec -w /workspace aqua-registry-windows bash -c rm aqua-checksums.json 2>/dev/null || : program=argd version=0.5.2
May  9 15:10:15.583 INF + /usr/bin/docker exec -w /workspace -e AQUA_GOOS=windows -e AQUA_GOARCH=arm64 -e AQUA_GITHUB_TOKEN= aqua-registry-windows aqua i program=argd version=0.5.2
May  9 15:10:15.632 INF Updating registry.yaml program=argd version=0.5.2

Executed the package:

❯ docker exec -w /workspace \
    -e AQUA_GOOS=linux \
    -e AQUA_GOARCH=amd64 \
    aqua-registry sh -c 'aqua i >/tmp/vector-aqua-i.log && vector --version'
vector 0.55.0 (x86_64-unknown-linux-musl cf8de83 2026-04-22 14:31:18.008404048)

Notes

Recent Vector releases no longer publish darwin/amd64 assets, so the latest override supports darwin/arm64 only.

AI assistance was used to scaffold, inspect, and test this change. I reviewed the generated configuration and test results.

---

https://vector.dev/docs/setup/installation/manual/from-archives/

Check List

• Read CONTRIBUTING.md
  • ⚠️ Avoid force push
  • ⚠️ Use argd s command when adding new packages
• Install and execute the package and confirm if the package works well

[kquinsland]

This is a replacement for #53516 . I didn't realize you had to explicitly configure an ssh key for signing.

[suzuki-shunsuke]

https://github.com/aquaproj/aqua-registry/blob/main/docs/add_package.md

argd s creates a commit, but please don't edit the commit by git commit --amend, git rebase, or somehow. argd s creates a commit to distinguish scaffolded code from manual changes. Please add new commits if you update code.

Ah, I see.
--local skips creating commit.
I'll remove this option.

• feat(scaffold)!: remove --local option registry-tool#1696

[kquinsland]

--local skips creating commit.
I'll remove this option.

Or update the docs so it's clear that --local is a testing/break-glass thing and not SOP?

In either case, what should I do with this PR?

[suzuki-shunsuke]

In either case, what should I do with this PR?

You don't need to do anything for the above comment.
I'm reviewing.