Skip to content

Commit dac266f

Browse files
committed
Merge branch 'main' into parse-syslog-force-format
2 parents d4e7f89 + fd302b0 commit dac266f

File tree

250 files changed

+8803
-3796
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

250 files changed

+8803
-3796
lines changed

.editorconfig

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,3 +27,6 @@ indent_size = 4
2727

2828
[*.svg]
2929
insert_final_newline = false
30+
31+
[*py]
32+
indent_size = 4

.github/ISSUE_TEMPLATE/bug.yml

Lines changed: 80 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,80 @@
1+
name: Bug
2+
description: 🐛 Let us know about an unexpected error, a crash, or an incorrect behavior.
3+
type: 'Bug'
4+
labels:
5+
- 'type: bug'
6+
body:
7+
- type: markdown
8+
attributes:
9+
value: |
10+
Thank you for opening a bug report! 🐛
11+
12+
- type: textarea
13+
attributes:
14+
label: A note for the community
15+
value: |
16+
<!-- Please keep this note for the community -->
17+
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
18+
* If you are interested in working on this issue or have submitted a pull request, please leave a comment.
19+
<!-- Thank you for keeping this note for the community -->
20+
21+
- type: textarea
22+
id: problem
23+
attributes:
24+
label: Problem
25+
description: >
26+
Please provide a clear and concise description of what the bug is,
27+
including what currently happens and what you expected to happen.
28+
validations:
29+
required: true
30+
31+
- type: textarea
32+
id: config
33+
attributes:
34+
label: VRL Program
35+
description: |
36+
Paste the relevant parts of your VRL program.
37+
38+
!! If your program contains sensitive information please redact it. !!
39+
render: text
40+
41+
- type: input
42+
id: version
43+
attributes:
44+
label: VRL and/or Vector Version
45+
description: |
46+
What VRL version is affected by this bug?
47+
48+
If you encountered this while running a Vector configuration, please paste the output of running `vector --version`.
49+
validations:
50+
required: true
51+
52+
- type: textarea
53+
id: debug
54+
attributes:
55+
label: Debug Output
56+
description: |
57+
Please share VRL diagnostics here.
58+
59+
!! Debug output may contain sensitive information. Please review it before posting publicly. !!
60+
render: text
61+
62+
- type: textarea
63+
id: data
64+
attributes:
65+
label: Example
66+
description: |
67+
Please share a VRL playground program. You can do this by clicking the `Share Program` button in
68+
https://playground.vrl.dev/ and share the URL.
69+
- type: textarea
70+
id: context
71+
attributes:
72+
label: Additional Context
73+
description: |
74+
Is there anything atypical about your situation that we should know? Are you running a custom version?
75+
- type: textarea
76+
id: references
77+
attributes:
78+
label: References
79+
description: |
80+
Are there any existing and related GitHub issues or Pull Requests that should be linked here?

.github/ISSUE_TEMPLATE/feature.yml

Lines changed: 72 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,72 @@
1+
name: Feature
2+
type: 'Feature'
3+
description: 🚀 Suggest a new feature.
4+
labels:
5+
- 'type: feature'
6+
body:
7+
- type: markdown
8+
attributes:
9+
value: |
10+
Thank you for opening a feature request! 🚀
11+
12+
For general questions about VRL usage, please see https://github.com/vectordotdev/vrl/discussions
13+
14+
- type: textarea
15+
attributes:
16+
label: A note for the community
17+
value: |
18+
<!-- Please keep this note for the community -->
19+
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
20+
* If you are interested in working on this issue or have submitted a pull request, please leave a comment.
21+
<!-- Thank you for keeping this note for the community -->
22+
23+
- type: textarea
24+
id: use-cases
25+
attributes:
26+
label: Use Cases
27+
description: |
28+
In order to properly evaluate a feature request, it is necessary to
29+
understand the use-cases for it.
30+
31+
Please describe below the _end goal_ you are trying to achieve that has
32+
led you to request this feature.
33+
34+
Please keep this section focused on the problem and not on the suggested
35+
solution. We'll get to that in a moment, below!
36+
37+
38+
- type: textarea
39+
id: attempted-solutions
40+
attributes:
41+
label: Attempted Solutions
42+
description: |
43+
If you've already tried to solve the problem within VRL's existing
44+
features and found a limitation that prevented you from succeeding, please
45+
describe it below in as much detail as possible.
46+
47+
Ideally, this would include real code snippets that you tried and what results you got in each case.
48+
49+
Please remove any sensitive information such as passwords before sharing code snippets and command lines.
50+
51+
- type: textarea
52+
id: proposal
53+
attributes:
54+
label: Proposal
55+
description: |
56+
If you have an idea for a way to address the problem via a change to
57+
VRL features, please describe it below.
58+
59+
In this section, it's helpful to include specific examples of how what
60+
you are suggesting might look in VRL code, or on the command line,
61+
since that allows us to understand the full picture of what you are proposing.
62+
63+
If you're not sure of some details, don't worry! When we evaluate the
64+
feature request we may suggest modifications as necessary to work within the
65+
design constraints of VRL.
66+
67+
- type: textarea
68+
id: references
69+
attributes:
70+
label: References
71+
description: |
72+
Are there any existing and related GitHub issues or Pull Requests that should be linked here?
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
---
2+
name: VRL minor release
3+
about: Use this template for a new minor release.
4+
title: "VRL [version] release"
5+
labels: "domain: releasing"
6+
---
7+
8+
- [ ] Create release preparation PR
9+
- [ ] Bump [Cargo.toml](https://github.com/vectordotdev/vrl/blob/main/Cargo.toml#L3) version and commit the change.
10+
- [ ] Run `cargo check` to update `Cargo.lock`.
11+
- [ ] Run the [./scripts/generate_release_changelog.sh](https://github.com/vectordotdev/vrl/blob/main/scripts/generate_release_changelog.sh) script
12+
and commit the changes.
13+
- [ ] After the above PR is merged, run the [./scripts/publish.py](https://github.com/vectordotdev/vrl/blob/main/scripts/publish.py) script.
14+
- [ ] Confirm that the new tag was created: https://github.com/vectordotdev/vrl/tags
15+
- [ ] Confirm that the new VRL release was published: https://crates.io/crates/vrl

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
<!--
2+
Your PR title must conform to the conventional commit spec:
3+
https://www.conventionalcommits.org/en/v1.0.0/
4+
5+
<type>(<scope>)!: <description>
6+
7+
* `type` = chore, enhancement, feat, fix, docs, revert
8+
* `!` = OPTIONAL: signals a breaking change
9+
* `scope` = Optional when `type` is "chore" or "docs"
10+
* `description` = short description of the change
11+
12+
Examples:
13+
14+
* enhancement(file source): Add `sort` option to sort discovered files
15+
* feat(new source): Initial `statsd` source
16+
* fix(file source): Fix a bug discovering new files
17+
* chore(external docs): Clarify `batch_size` option
18+
-->
19+
20+
## Summary
21+
22+
<!-- Please provide a brief summary about what this PR does.
23+
This should help the reviewers give feedback faster and with higher quality. -->
24+
25+
## Change Type
26+
27+
- [ ] Bug fix
28+
- [ ] New feature
29+
- [ ] Non-functional (chore, refactoring, docs)
30+
- [ ] Performance
31+
32+
## Is this a breaking change?
33+
34+
- [ ] Yes
35+
- [ ] No
36+
37+
## How did you test this PR?
38+
39+
<!-- Please describe your testing plan here.
40+
Providing this information upfront will facilitate a smoother review process. -->
41+
42+
## Does this PR include user facing changes?
43+
44+
- [ ] Yes. Please add a changelog fragment based on
45+
our [guidelines](https://github.com/vectordotdev/vector/blob/master/changelog.d/README.md).
46+
- [ ] No. A maintainer will apply the "no-changelog" label to this PR.
47+
48+
## Checklist
49+
50+
- [ ] Our [CONTRIBUTING.md](https://github.com/vectordotdev/vrl/blob/main/CONTRIBUTING.md) is a good starting place.
51+
- [ ] If this PR introduces changes to [LICENSE-3rdparty.csv](https://github.com/vectordotdev/vrl/blob/main/LICENSE-3rdparty.csv), please
52+
run `dd-rust-license-tool write` and commit the changes. More details [here](https://crates.io/crates/dd-rust-license-tool).
53+
- [ ] For new VRL functions, please also create a sibling PR in Vector to document the new function.
54+
55+
<!-- Examples for the above:
56+
PR adding new VRL function: https://github.com/vectordotdev/vrl/pull/993
57+
PR adding documentation: https://github.com/vectordotdev/vector/pull/21142
58+
59+
We are working towards improving this workflow.
60+
-->
61+
62+
## References
63+
64+
<!-- Please list any issues closed by this PR. -->
65+
66+
<!--
67+
- Closes: <issue link>
68+
-->
69+
70+
<!-- Any other issues or PRs relevant to this PR? Feel free to list them here. -->

.github/dependabot.yml

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,10 @@ version: 2
22
updates:
33
- package-ecosystem: "cargo"
44
directory: "/"
5+
allow:
6+
- dependency-type: "all"
57
schedule:
6-
interval: "daily"
8+
interval: "monthly"
79
time: "04:00" # UTC
810
labels:
911
- "domain: deps"
@@ -12,14 +14,20 @@ updates:
1214
prefix: "chore(deps)"
1315
open-pull-requests-limit: 10
1416
groups:
17+
patches:
18+
applies-to: version-updates
19+
patterns:
20+
- "*"
21+
update-types:
22+
- "patch"
1523
prost:
1624
patterns:
1725
- "prost"
1826
- "prost-*"
1927
- package-ecosystem: "github-actions"
2028
directory: "/"
2129
schedule:
22-
interval: "daily"
30+
interval: "monthly"
2331
labels:
2432
- "domain: ci"
2533
- "no-changelog"

0 commit comments

Comments
 (0)