feat(new source): add Azure Blob Storage source

.cargo/config.toml

@@ -2,12 +2,15 @@
 vdev = "run --quiet --package vdev --"
 
 [env]
-# Build with large pages so that Vector runs on systems with 64k pages or less (e.g. 4k) to support
-# CentOS 7, 8, and a few other Linux distributions.
+# Build jemalloc assuming 64K pages so binaries also run on aarch64 hosts whose
+# kernels ship with a 64K page size (notably EL8 aarch64). On 4K-page hosts this
+# coarsens jemalloc's allocation granularity; no regression was measured in
+# https://github.com/vectordotdev/vector/pull/18481.
 JEMALLOC_SYS_WITH_LG_PAGE = "16"
 
 [target.'cfg(all())']
 rustflags = [
+  "-D", "warnings",
   "-Dclippy::print_stdout",
   "-Dclippy::print_stderr",
   "-Dclippy::dbg_macro",
@@ -35,4 +38,4 @@ rustflags = ["-C", "link-args=-rdynamic"]
 
 [target.x86_64-pc-windows-msvc]
 # https://github.com/dtolnay/inventory/issues/58
-rustflags = ["-C", "codegen-units=1"]
+rustflags = ["-C", "codegen-units=1", "-Ctarget-feature=+crt-static"]

.github/CODEOWNERS

@@ -3,13 +3,15 @@
 .github/workflows/regression.yml @vectordotdev/vector @vectordotdev/single-machine-performance
 regression/config.yaml @vectordotdev/vector @vectordotdev/single-machine-performance
 
-docs/ @vectordotdev/vector @vectordotdev/documentation
 website/ @vectordotdev/vector
-website/content @vectordotdev/vector @vectordotdev/documentation
-website/cue/reference @vectordotdev/vector @vectordotdev/documentation
-
 website/js @vectordotdev/vector @vectordotdev/vector-website
 website/layouts @vectordotdev/vector @vectordotdev/vector-website
 website/scripts @vectordotdev/vector @vectordotdev/vector-website
 website/data @vectordotdev/vector @vectordotdev/vector-website
 website/* @vectordotdev/vector @vectordotdev/vector-website
+
+# Keep documentation team paths in sync with .github/workflows/add_docs_review_label.yml
+/*.md @vectordotdev/vector @vectordotdev/documentation
+docs/ @vectordotdev/vector @vectordotdev/documentation
+website/content @vectordotdev/vector @vectordotdev/documentation
+website/cue/reference @vectordotdev/vector @vectordotdev/documentation

.github/DISCUSSION_TEMPLATE/q-a.yml

@@ -1,5 +1,5 @@
 title: "Q&A"
-labels: [ q-a ]
+labels: [q-a]
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/bug.yml

@@ -1,94 +1,94 @@
 name: Bug
 description: 🐛 Let us know about an unexpected error, a crash, or an incorrect behavior.
-type: 'Bug'
+type: "Bug"
 body:
-- type: markdown
-  attributes:
-    value: |
-      Thank you for opening 🐛 bug report!
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for opening 🐛 bug report!
 
-- type: textarea
-  attributes:
-    label: A note for the community
-    value: |
-      <!-- Please keep this note for the community -->
-      * 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
-      * If you are interested in working on this issue or have submitted a pull request, please leave a comment
-      <!-- Thank you for keeping this note for the community -->
+  - type: textarea
+    attributes:
+      label: A note for the community
+      value: |
+        <!-- Please keep this note for the community -->
+        * 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
+        * If you are interested in working on this issue or have submitted a pull request, please leave a comment
+        <!-- Thank you for keeping this note for the community -->
 
-- type: textarea
-  id: problem
-  attributes:
-    label: Problem
-    description: >
-      Please provide a clear and concise description of what the bug is,
-      including what currently happens and what you expected to happen.
-  validations:
-    required: true
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem
+      description: >
+        Please provide a clear and concise description of what the bug is,
+        including what currently happens and what you expected to happen.
+    validations:
+      required: true
 
-- type: textarea
-  id: config
-  attributes:
-    label: Configuration
-    description: |
-      Paste the relevant parts of your Vector configuration file.
+  - type: textarea
+    id: config
+    attributes:
+      label: Configuration
+      description: |
+        Paste the relevant parts of your Vector configuration file.
 
-      !! If your config files contain sensitive information please remove it !!
-    render: text
+        !! If your config files contain sensitive information please remove it !!
+      render: text
 
-- type: input
-  id: version
-  attributes:
-    label: Version
-    description: |
-      Please paste the output of running `vector --version`.
+  - type: input
+    id: version
+    attributes:
+      label: Version
+      description: |
+        Please paste the output of running `vector --version`.
 
-      If you are not running the latest version of Vector, please try upgrading
-      because your issue may have already been fixed.
-  validations:
-    required: true
+        If you are not running the latest version of Vector, please try upgrading
+        because your issue may have already been fixed.
+    validations:
+      required: true
 
-- type: textarea
-  id: debug
-  attributes:
-    label: Debug Output
-    description: |
-      Full debug output can be obtained by running Vector with the following:
+  - type: textarea
+    id: debug
+    attributes:
+      label: Debug Output
+      description: |
+        Full debug output can be obtained by running Vector with the following:
 
-      ```
-      RUST_BACKTRACE=full vector -vvv <rest of commands>
-      ```
+        ```
+        RUST_BACKTRACE=full vector -vvv <rest of commands>
+        ```
 
-      If the debug output is long, please create a GitHub Gist containing the debug output and paste the link here.
+        If the debug output is long, please create a GitHub Gist containing the debug output and paste the link here.
 
-      !! Debug output may contain sensitive information. Please review it before posting publicly. !!
-    render: text
+        !! Debug output may contain sensitive information. Please review it before posting publicly. !!
+      render: text
 
-- type: textarea
-  id: data
-  attributes:
-    label: Example Data
-    description: |
-      Please provide any example data that will help debug the issue, for example:
+  - type: textarea
+    id: data
+    attributes:
+      label: Example Data
+      description: |
+        Please provide any example data that will help debug the issue, for example:
 
-      ```
-      201.69.207.46 - kemmer6752 [07/06/2019:14:53:55 -0400] "PATCH /innovative/interfaces" 301 669
-      ```
+        ```
+        201.69.207.46 - kemmer6752 [07/06/2019:14:53:55 -0400] "PATCH /innovative/interfaces" 301 669
+        ```
 
-- type: textarea
-  id: context
-  attributes:
-    label: Additional Context
-    description: |
-      Is there anything atypical about your situation that we should know? For
-      example: is Vector running in Kubernetes? Are you passing any unusual command
-      line options or environment variables to opt-in to non-default behavior?
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      description: |
+        Is there anything atypical about your situation that we should know? For
+        example: is Vector running in Kubernetes? Are you passing any unusual command
+        line options or environment variables to opt-in to non-default behavior?
 
-- type: textarea
-  id: references
-  attributes:
-    label: References
-    description: |
-      Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:
+  - type: textarea
+    id: references
+    attributes:
+      label: References
+      description: |
+        Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:
 
-      - #6017
+        - #6017

.github/ISSUE_TEMPLATE/config.yml

@@ -12,4 +12,3 @@ contact_links:
   - name: Twitter
     url: https://twitter.com/vectordotdev
     about: Follow us and stay up to date with Vector.
-

.github/ISSUE_TEMPLATE/feature.yml

@@ -1,87 +1,86 @@
 name: Feature
-type: 'Feature'
+type: "Feature"
 description: 🚀 Suggest a new feature.
 body:
-- type: markdown
-  attributes:
-    value: |
-      Thank you for opening 🚀 feature request!
-
-      For general questions about Vector usage, please see
-      https://discussions.vector.dev.
-
-- type: textarea
-  attributes:
-    label: A note for the community
-    value: |
-      <!-- Please keep this note for the community -->
-      * 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
-      * If you are interested in working on this issue or have submitted a pull request, please leave a comment
-      <!-- Thank you for keeping this note for the community -->
-
-- type: textarea
-  id: use-cases
-  attributes:
-    label: Use Cases
-    description: |
-      In order to properly evaluate a feature request, it is necessary to
-      understand the use-cases for it.
-
-      Please describe below the _end goal_ you are trying to achieve that has
-      led you to request this feature.
-
-      Please keep this section focused on the problem and not on the suggested
-      solution. We'll get to that in a moment, below!
-
-
-- type: textarea
-  id: attempted-solutions
-  attributes:
-    label: Attempted Solutions
-    description: |
-      If you've already tried to solve the problem within Vector's existing
-      features and found a limitation that prevented you from succeeding, please
-      describe it below in as much detail as possible.
-
-      Ideally, this would include real configuration snippets that you tried
-      and what results you got in each case.
-
-      Please remove any sensitive information such as passwords before sharing
-      configuration snippets and command lines.
-
-- type: textarea
-  id: proposal
-  attributes:
-    label: Proposal
-    description: |
-      If you have an idea for a way to address the problem via a change to
-      Vector features, please describe it below.
-
-      In this section, it's helpful to include specific examples of how what
-      you are suggesting might look in configuration files, or on the command line,
-      since that allows us to understand the full picture of what you are proposing.
-
-      If you're not sure of some details, don't worry! When we evaluate the
-      feature request we may suggest modifications as necessary to work within the
-      design constraints of Vector.
-
-- type: textarea
-  id: references
-  attributes:
-    label: References
-    description: |
-      Are there any other GitHub issues, whether open or closed, that are
-      related to the problem you've described above or to the suggested solution? If
-      so, please create a list below that mentions each of them. For example:
-
-      - #7023
-
-- type: input
-  id: version
-  attributes:
-    label: Version
-    description: |
-      Please paste the output of running `vector --version`.
-
-      This will record which version was current at the time of your feature request,
-      to help manage the request backlog.
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for opening 🚀 feature request!
+
+        For general questions about Vector usage, please see
+        https://discussions.vector.dev.
+
+  - type: textarea
+    attributes:
+      label: A note for the community
+      value: |
+        <!-- Please keep this note for the community -->
+        * 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
+        * If you are interested in working on this issue or have submitted a pull request, please leave a comment
+        <!-- Thank you for keeping this note for the community -->
+
+  - type: textarea
+    id: use-cases
+    attributes:
+      label: Use Cases
+      description: |
+        In order to properly evaluate a feature request, it is necessary to
+        understand the use-cases for it.
+
+        Please describe below the _end goal_ you are trying to achieve that has
+        led you to request this feature.
+
+        Please keep this section focused on the problem and not on the suggested
+        solution. We'll get to that in a moment, below!
+
+  - type: textarea
+    id: attempted-solutions
+    attributes:
+      label: Attempted Solutions
+      description: |
+        If you've already tried to solve the problem within Vector's existing
+        features and found a limitation that prevented you from succeeding, please
+        describe it below in as much detail as possible.
+
+        Ideally, this would include real configuration snippets that you tried
+        and what results you got in each case.
+
+        Please remove any sensitive information such as passwords before sharing
+        configuration snippets and command lines.
+
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposal
+      description: |
+        If you have an idea for a way to address the problem via a change to
+        Vector features, please describe it below.
+
+        In this section, it's helpful to include specific examples of how what
+        you are suggesting might look in configuration files, or on the command line,
+        since that allows us to understand the full picture of what you are proposing.
+
+        If you're not sure of some details, don't worry! When we evaluate the
+        feature request we may suggest modifications as necessary to work within the
+        design constraints of Vector.
+
+  - type: textarea
+    id: references
+    attributes:
+      label: References
+      description: |
+        Are there any other GitHub issues, whether open or closed, that are
+        related to the problem you've described above or to the suggested solution? If
+        so, please create a list below that mentions each of them. For example:
+
+        - #7023
+
+  - type: input
+    id: version
+    attributes:
+      label: Version
+      description: |
+        Please paste the output of running `vector --version`.
+
+        This will record which version was current at the time of your feature request,
+        to help manage the request backlog.