Skip to content

Conversation

pront
Copy link
Member

@pront pront commented Sep 26, 2025

Summary

LLM generated - Needs review.

Vector configuration

How did you test this PR?

Change Type

  • Bug fix
  • New feature
  • Non-functional (chore, refactoring, docs)
  • Performance

Is this a breaking change?

  • Yes
  • No

Does this PR include user facing changes?

  • Yes. Please add a changelog fragment based on our guidelines.
  • No. A maintainer will apply the no-changelog label to this PR.

References

Notes

  • Please read our Vector contributor resources.
  • Do not hesitate to use @vectordotdev/vector to reach out to us regarding this PR.
  • Some CI checks run only after we manually approve them.
    • We recommend adding a pre-push hook, please see this template.
    • Alternatively, we recommend running the following locally before pushing to the remote branch:
      • make fmt
      • make check-clippy (if there are failures it's possible some of them can be fixed with make clippy-fix)
      • make test
  • After a review is requested, please avoid force pushes to help us review incrementally.
    • Feel free to push as many commits as you want. They will be squashed into one before merging.
    • For example, you can run git merge origin master and git push.
  • If this PR introduces changes Vector dependencies (modifies Cargo.lock), please
    run make build-licenses to regenerate the license inventory and commit the changes (if any). More details here.

# Code quality checks
make check # Format, clippy, docs
make check-fmt # Format checking only
make check-clippy # Linting only

Check failure

Code scanning / check-spelling

Unrecognized Spelling Error

Linting is not a recognized word. (unrecognized-spelling)

### Quality Gates
- **Code Formatting**: rustfmt enforcement
- **Linting**: Clippy with custom rules

Check failure

Code scanning / check-spelling

Unrecognized Spelling Error

Linting is not a recognized word. (unrecognized-spelling)
- `api/` - GraphQL API for management and monitoring
- `cli.rs` - Command-line interface

- `/lib/` - Modular library crates
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

missing vector-lib

Comment on lines +42 to +51
#### Environment Setup
```bash
# Use containerized development environment (recommended for new contributors)
export CONTAINER_TOOL="podman" # Optional: default is docker
make environment # Enter development shell

# Or setup native environment
cargo install -f --path vdev # Install Vector development CLI
```

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
#### Environment Setup
```bash
# Use containerized development environment (recommended for new contributors)
export CONTAINER_TOOL="podman" # Optional: default is docker
make environment # Enter development shell
# Or setup native environment
cargo install -f --path vdev # Install Vector development CLI
```

We don't want to actually develop inside the environment or to install vdev when we can use cargo vdev instead

Comment on lines +54 to +57
# Development build
make build-dev
# or in container
make build-dev ENVIRONMENT=true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably replace this with cargo commands and also instruct to use --no-default-features --features="foo,bar,baz" to improve compile times

make test-integration

# Specific integration test
make test-integration-SCOPE="kafka"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
make test-integration-SCOPE="kafka"
make test-integration-kafka

I think -SCOPE is wrong

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants