LOG-9344: add context files for agentic SDLC#269
Conversation
Create four comprehensive context files on rh-main to orient AI agents and developers to this Red Hat fork of Vector: - AGENTS.md: Fork-specific quick reference (branch selection, ocp-logging feature scope, patched crates, build commands, OWNERS, Jira conventions) with pointers to upstream docs for generic Vector development - CONTRIBUTING.md: Fork-focused contribution guide (branching strategy, PR process, code review, Jira conventions, upstream contribution workflow) - ARCHITECTURE.md: Fork architecture (deployment model, ocp-logging feature tables for both v0.47.0-rh and v0.54.0-rh, patched dependencies with rationale, build system, design decisions, upstream sync strategy) - CLAUDE.md: Stub pointing to AGENTS.md (matches dev branch pattern) - README.md: Updated with doc links, quick-start build snippet, v0.54.0-rh release entry, fixed formatting All ocp-logging component lists (sources, transforms, sinks) verified against actual Cargo.toml on both dev branches. No upstream duplication — files reference upstream docs for generic Vector content. Upstream files on dev branches left untouched to avoid merge conflicts. Fixes LOG-9344 Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
|
@vparfonov: This pull request references LOG-9344 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/retest |
| ### Build constraints | ||
|
|
||
| - **`lld` linker**: Configured in `.cargo/config.toml`. GNU ld runs out of memory during linking. | ||
| - **`protoc` bundled**: Pre-built binaries in `thirdparty/protoc/` (architecture-aware). No network download during build. |
There was a problem hiding this comment.
we can remove this now we are not bundling it
|
|
||
| ### CI/CD | ||
|
|
||
| No in-repo CI pipelines. Builds happen in Red Hat's internal ART/OSBS infrastructure: |
There was a problem hiding this comment.
just say "internal infrastructure"
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jcantrill, vparfonov The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
3 participants
Create four comprehensive context files on rh-main to orient AI agents and developers to this Red Hat fork of Vector:
AGENTS.md: Fork-specific quick reference (branch selection, ocp-logging feature scope, patched crates, build commands, OWNERS, Jira conventions) with pointers to upstream docs for generic Vector development
CONTRIBUTING.md: Fork-focused contribution guide (branching strategy, PR process, code review, Jira conventions, upstream contribution workflow)
ARCHITECTURE.md: Fork architecture (deployment model, ocp-logging feature tables for both v0.47.0-rh and v0.54.0-rh, patched dependencies with rationale, build system, design decisions, upstream sync strategy)
CLAUDE.md: Stub pointing to AGENTS.md (matches dev branch pattern)
README.md: Updated with doc links, quick-start build snippet, v0.54.0-rh release entry, fixed formatting
All ocp-logging component lists (sources, transforms, sinks) verified against actual Cargo.toml on both dev branches. No upstream duplication — files reference upstream docs for generic Vector content. Upstream files on dev branches left untouched to avoid merge conflicts.
Fixes LOG-9344