|
1 | 1 | name: Feature |
2 | | -type: 'Feature' |
| 2 | +type: "Feature" |
3 | 3 | description: 🚀 Suggest a new feature. |
4 | 4 | body: |
5 | | -- type: markdown |
6 | | - attributes: |
7 | | - value: | |
8 | | - Thank you for opening 🚀 feature request! |
9 | | -
|
10 | | - For general questions about Vector usage, please see |
11 | | - https://discussions.vector.dev. |
12 | | -
|
13 | | -- type: textarea |
14 | | - attributes: |
15 | | - label: A note for the community |
16 | | - value: | |
17 | | - <!-- Please keep this note for the community --> |
18 | | - * 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 |
19 | | - * If you are interested in working on this issue or have submitted a pull request, please leave a comment |
20 | | - <!-- Thank you for keeping this note for the community --> |
21 | | -
|
22 | | -- type: textarea |
23 | | - id: use-cases |
24 | | - attributes: |
25 | | - label: Use Cases |
26 | | - description: | |
27 | | - In order to properly evaluate a feature request, it is necessary to |
28 | | - understand the use-cases for it. |
29 | | -
|
30 | | - Please describe below the _end goal_ you are trying to achieve that has |
31 | | - led you to request this feature. |
32 | | -
|
33 | | - Please keep this section focused on the problem and not on the suggested |
34 | | - solution. We'll get to that in a moment, below! |
35 | | -
|
36 | | -
|
37 | | -- type: textarea |
38 | | - id: attempted-solutions |
39 | | - attributes: |
40 | | - label: Attempted Solutions |
41 | | - description: | |
42 | | - If you've already tried to solve the problem within Vector's existing |
43 | | - features and found a limitation that prevented you from succeeding, please |
44 | | - describe it below in as much detail as possible. |
45 | | -
|
46 | | - Ideally, this would include real configuration snippets that you tried |
47 | | - and what results you got in each case. |
48 | | -
|
49 | | - Please remove any sensitive information such as passwords before sharing |
50 | | - configuration snippets and command lines. |
51 | | -
|
52 | | -- type: textarea |
53 | | - id: proposal |
54 | | - attributes: |
55 | | - label: Proposal |
56 | | - description: | |
57 | | - If you have an idea for a way to address the problem via a change to |
58 | | - Vector features, please describe it below. |
59 | | -
|
60 | | - In this section, it's helpful to include specific examples of how what |
61 | | - you are suggesting might look in configuration files, or on the command line, |
62 | | - since that allows us to understand the full picture of what you are proposing. |
63 | | -
|
64 | | - If you're not sure of some details, don't worry! When we evaluate the |
65 | | - feature request we may suggest modifications as necessary to work within the |
66 | | - design constraints of Vector. |
67 | | -
|
68 | | -- type: textarea |
69 | | - id: references |
70 | | - attributes: |
71 | | - label: References |
72 | | - description: | |
73 | | - Are there any other GitHub issues, whether open or closed, that are |
74 | | - related to the problem you've described above or to the suggested solution? If |
75 | | - so, please create a list below that mentions each of them. For example: |
76 | | -
|
77 | | - - #7023 |
78 | | -
|
79 | | -- type: input |
80 | | - id: version |
81 | | - attributes: |
82 | | - label: Version |
83 | | - description: | |
84 | | - Please paste the output of running `vector --version`. |
85 | | -
|
86 | | - This will record which version was current at the time of your feature request, |
87 | | - to help manage the request backlog. |
| 5 | + - type: markdown |
| 6 | + attributes: |
| 7 | + value: | |
| 8 | + Thank you for opening 🚀 feature request! |
| 9 | +
|
| 10 | + For general questions about Vector usage, please see |
| 11 | + https://discussions.vector.dev. |
| 12 | +
|
| 13 | + - type: textarea |
| 14 | + attributes: |
| 15 | + label: A note for the community |
| 16 | + value: | |
| 17 | + <!-- Please keep this note for the community --> |
| 18 | + * 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 |
| 19 | + * If you are interested in working on this issue or have submitted a pull request, please leave a comment |
| 20 | + <!-- Thank you for keeping this note for the community --> |
| 21 | +
|
| 22 | + - type: textarea |
| 23 | + id: use-cases |
| 24 | + attributes: |
| 25 | + label: Use Cases |
| 26 | + description: | |
| 27 | + In order to properly evaluate a feature request, it is necessary to |
| 28 | + understand the use-cases for it. |
| 29 | +
|
| 30 | + Please describe below the _end goal_ you are trying to achieve that has |
| 31 | + led you to request this feature. |
| 32 | +
|
| 33 | + Please keep this section focused on the problem and not on the suggested |
| 34 | + solution. We'll get to that in a moment, below! |
| 35 | +
|
| 36 | + - type: textarea |
| 37 | + id: attempted-solutions |
| 38 | + attributes: |
| 39 | + label: Attempted Solutions |
| 40 | + description: | |
| 41 | + If you've already tried to solve the problem within Vector's existing |
| 42 | + features and found a limitation that prevented you from succeeding, please |
| 43 | + describe it below in as much detail as possible. |
| 44 | +
|
| 45 | + Ideally, this would include real configuration snippets that you tried |
| 46 | + and what results you got in each case. |
| 47 | +
|
| 48 | + Please remove any sensitive information such as passwords before sharing |
| 49 | + configuration 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 | + Vector 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 configuration files, 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 Vector. |
| 66 | +
|
| 67 | + - type: textarea |
| 68 | + id: references |
| 69 | + attributes: |
| 70 | + label: References |
| 71 | + description: | |
| 72 | + Are there any other GitHub issues, whether open or closed, that are |
| 73 | + related to the problem you've described above or to the suggested solution? If |
| 74 | + so, please create a list below that mentions each of them. For example: |
| 75 | +
|
| 76 | + - #7023 |
| 77 | +
|
| 78 | + - type: input |
| 79 | + id: version |
| 80 | + attributes: |
| 81 | + label: Version |
| 82 | + description: | |
| 83 | + Please paste the output of running `vector --version`. |
| 84 | +
|
| 85 | + This will record which version was current at the time of your feature request, |
| 86 | + to help manage the request backlog. |
0 commit comments