Merge branch 'main' into vault-24407/plugin-and-pinned-versions-support

.github/ISSUE_TEMPLATE/00_bug_report.yml

@@ -11,15 +11,9 @@ body:
       value: |
         # Thank you for raising a bug report!
 
-        Before submitting a bug report, we ask that you first search existing
-        issues to see if someone else may have experienced the same issue. This
-        helps to keep all relevant information in one place, including any
-        potential workarounds.
+        Before submitting a bug report, we ask that you first search existing issues to see if someone else may have experienced the same issue. This helps to keep all relevant information in one place, including any potential workarounds.
 
-        We also ask that you consider whether your issue may be related to
-        Terraform Core. If you are running into one of the following scenarios,
-        we recommend [opening an issue](https://github.com/hashicorp/terraform/issues/new/choose)
-        in the Terraform Core repository instead:
+        We also ask that you consider whether your issue may be related to Terraform Core. If you are running into one of the following scenarios, we recommend [opening an issue](https://github.com/hashicorp/terraform/issues/new/choose) in the Terraform Core repository instead:
 
         * [Configuration Language](https://www.terraform.io/docs/configuration/index.html) or resource ordering issues
         * [State](https://www.terraform.io/docs/state/index.html) and [State Backend](https://www.terraform.io/docs/backends/index.html) issues
@@ -32,10 +26,7 @@ body:
       value: |
         # Terraform and Vault Provider Versions
 
-        Please run `terraform -v` to show the Terraform Core and provider
-        version(s). If you are not running the latest version of either the
-        provider or Terraform Core, please consider upgrading, as your issue
-        may have already been fixed.
+        Please run `terraform -v` to show the Terraform Core and provider version(s). If you are not running the latest version of either the provider or Terraform Core, please consider upgrading, as your issue may have already been fixed.
 
         [Terraform documentation on provider versioning](https://www.terraform.io/docs/configuration/providers.html#provider-versions)
 
@@ -44,8 +35,7 @@ body:
     attributes:
       label: Terraform Core Version
       description: |
-        The semantic version of Terraform Core used when experiencing the bug.
-        If multiple versions have been tested, a comma separated list.
+        The semantic version of Terraform Core used when experiencing the bug. If multiple versions have been tested, a comma separated list.
       placeholder: "X.Y.Z"
     validations:
       required: true
@@ -55,9 +45,7 @@ body:
     attributes:
       label: Terraform Vault Provider Version
       description: |
-        The semantic version of the Terraform Vault Provider used when
-        experiencing the bug. If multiple versions have been tested, a comma
-        separated list.
+        The semantic version of the Terraform Vault Provider used when experiencing the bug. If multiple versions have been tested, a comma separated list.
       placeholder: "X.Y.Z"
     validations:
       required: true
@@ -67,9 +55,7 @@ body:
     attributes:
       label: Vault Server Version
       description: |
-        The semantic version of the Vault Server used when experiencing the
-        bug. If multiple versions have been tested, a comma
-        separated list.
+        The semantic version of the Vault Server used when experiencing the bug. If multiple versions have been tested, a comma separated list.
       placeholder: "X.Y.Z"
     validations:
       required: true
@@ -79,14 +65,9 @@ body:
       value: |
         # Description
 
-        In the next few fields, please provide any useful information you can
-        around what resources are affected, what you expected to happen, and
-        what actually happened. There is also a field to optionally provide a
-        small snippet of any relevant error or panic output.
+        In the next few fields, please provide any useful information you can around what resources are affected, what you expected to happen, and what actually happened. There is also a field to optionally provide a small snippet of any relevant error or panic output.
 
-        Note that there is a section later in the form to provide more complete
-        Terraform configuration and logging information. These fields should
-        instead be thought of as the place to briefly describe the bug.
+        Note that there is a section later in the form to provide more complete Terraform configuration and logging information. These fields should instead be thought of as the place to briefly describe the bug.
 
   - type: textarea
     id: affected
@@ -118,9 +99,7 @@ body:
     attributes:
       label: Relevant Error/Panic Output Snippet
       description: |
-        If applicable, provide a relevant snippet from the error or panic
-        output. This will be rendered as `shell`, so there is no need to add a
-        [code fence](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks).
+        If applicable, provide a relevant snippet from the error or panic output. This will be rendered as `shell`, so there is no need to add a [code fence](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks).
       render: shell
     validations:
       required: false
@@ -130,30 +109,20 @@ body:
       value: |
         # Configuration and Logging
 
-        Here, we ask that you provide the Terraform configuration and, when
-        possible, the debug logs. For configurations or logs of more than just
-        a few lines, it's preferred to either share a Gist link or zip the
-        files and upload them.
+        Here, we ask that you provide the Terraform configuration and, when possible, the debug logs. For configurations or logs of more than just a few lines, it's preferred to either share a Gist link or zip the files and upload them.
 
-        Terraform configurations or debug logs under 25MB may be
-        [attached directly in the field](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/attaching-files).
-        Files larger than this should be uploaded to a file hosting service and
-        a link shared.
+        Terraform configurations or debug logs under 25MB may be [attached directly in the field](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/attaching-files).  Files larger than this should be uploaded to a file hosting service and a link shared.
 
         For your security you can also encrypt the files using our [GPG public key](https://keybase.io/hashicorp).
 
-        **Note:** These form fields do not automatically render, so you will
-        need to use [code fence(s)](https://help.github.com/articles/basic-writing-and-formatting-syntax/#quoting-code)
-        to achieve proper formatting.
+        **Note:** These form fields do not automatically render, so you will need to use [code fence(s)](https://help.github.com/articles/basic-writing-and-formatting-syntax/#quoting-code) to achieve proper formatting.
 
   - type: textarea
     id: tf_config
     attributes:
       label: Terraform Configuration Files
       description: |
-        Please paste, upload, or link to a file or Gist containing all
-        Terraform configurations required to reproduce the bug. See note above
-        for additional information on file size restrictions and encrypting.
+        Please paste, upload, or link to a file or Gist containing all Terraform configurations required to reproduce the bug. See note above for additional information on file size restrictions and encrypting.
 
         Bug reports without a functional reproduction may be closed without investigation.
     validations:
@@ -172,12 +141,9 @@ body:
     attributes:
       label: Debug Output
       description: |
-        If possible, please paste, upload, or link to a file or Gist containing
-        debug logs. See note above for additional information on file size
-        restrictions and encrypting.
+        If possible, please paste, upload, or link to a file or Gist containing debug logs. See note above for additional information on file size restrictions and encrypting.
 
-        To obtain the debug output, see the
-        [Terraform documentation on debugging](https://www.terraform.io/docs/internals/debugging.html).
+        To obtain the debug output, see the [Terraform documentation on debugging](https://www.terraform.io/docs/internals/debugging.html).
     validations:
       required: false
 
@@ -186,8 +152,7 @@ body:
     attributes:
       label: Panic Output
       description: |
-        If Terraform produced a panic, please paste, upload, or link to a file
-        or Gist containing the output of the `crash.log`.
+        If Terraform produced a panic, please paste, upload, or link to a file or Gist containing the output of the `crash.log`.
     validations:
       required: false
 
@@ -196,18 +161,13 @@ body:
       value: |
         # Additional Information
 
-        For the final two fields, optionally provide any additional context
-        that might help the community or maintainers to investigate the bug.
-        This might be additional references that you found when
-        troubleshooting, similar bug reports, or specifics about your
-        environment that might be unique.
+        For the final two fields, optionally provide any additional context that might help the community or maintainers to investigate the bug.  This might be additional references that you found when troubleshooting, similar bug reports, or specifics about your environment that might be unique.
 
   - type: textarea
     attributes:
       label: Important Factoids
       description: |
-        Are there anything atypical about your configuration or environment
-        that we should know about?
+        Are there anything atypical about your configuration or environment that we should know about?
     validations:
       required: false
 
@@ -217,9 +177,7 @@ body:
       placeholder: "* GH-1234"
       label: References
       description: |
-        Where possible, please supply links to Vault documentation, other
-        GitHub issues (open or closed) or pull requests that give additional
-        context.
+        Where possible, please supply links to Vault documentation, other GitHub issues (open or closed) or pull requests that give additional context.
 
         [Information about referencing Github Issues](https://help.github.com/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests)
     validations:
@@ -230,11 +188,7 @@ body:
     attributes:
       label: Would you like to implement a fix?
       description: |
-        If you plan to implement a fix for this, check this box to let the
-        maintainers and community know (you can update this later if you change
-        your mind). If this would be your first contribution, refer to
-        [Developing the Provider](https://github.com/hashicorp/terraform-provider-vault#developing-the-provider)
-        for tips on getting started.
+        If you plan to implement a fix for this, check this box to let the maintainers and community know (you can update this later if you change your mind). If this would be your first contribution, refer to [Developing the Provider](https://github.com/hashicorp/terraform-provider-vault#developing-the-provider) for tips on getting started.
       options:
         - "No"
         - "Yes"

.github/ISSUE_TEMPLATE/01_documentation.yml

@@ -11,12 +11,9 @@ body:
       value: |
         # Thank you for raising a documentation issue!
 
-        This form is meant to alert the maintainers to an issue with the
-        provider documentation found on the [Terraform Registry](https://registry.terraform.io/providers/hashicorp/vault/latest)
-        such as resource and data source documentation, guides and examples.
+        This form is meant to alert the maintainers to an issue with the provider documentation found on the [Terraform Registry](https://registry.terraform.io/providers/hashicorp/vault/latest) such as resource and data source documentation, guides and examples.
 
-        Documentation edits are generally a bit less involved, so are often a
-        great entrypoint if you've ever been interested in contributing.
+        Documentation edits are generally a bit less involved, so are often a great entrypoint if you've ever been interested in contributing.
 
   - type: input
     id: registry_link
@@ -39,9 +36,7 @@ body:
     attributes:
       label: References
       description: |
-        Where possible, please supply links to Vault documentation, other
-        GitHub issues (open or closed) or pull requests that give additional
-        context.
+        Where possible, please supply links to Vault documentation, other GitHub issues (open or closed) or pull requests that give additional context.
 
         [Information about referencing Github Issues](https://help.github.com/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests)
     validations:
@@ -52,11 +47,7 @@ body:
     attributes:
       label: Would you like to implement a fix?
       description: |
-        If you plan to implement a fix for this, check this box to let the
-        maintainers and community know (you can update this later if you change
-        your mind). If this would be your first contribution, refer to
-        [Developing the Provider](https://github.com/hashicorp/terraform-provider-vault#developing-the-provider)
-        for tips on getting started.
+        If you plan to implement a fix for this, check this box to let the maintainers and community know (you can update this later if you change your mind). If this would be your first contribution, refer to [Developing the Provider](https://github.com/hashicorp/terraform-provider-vault#developing-the-provider) for tips on getting started.
       options:
         - "No"
         - "Yes"

.github/ISSUE_TEMPLATE/02_enhancement.yml

@@ -11,16 +11,9 @@ body:
       value: |
         # Thank you for opening an enhancement request!
 
-        This form is intended as a way to request additional functionality for
-        existing resources, data sources, or the provider itself. This may
-        include requests such as adding additional arguments or attributes
-        enabled by upstream API changes, additional validation for arguments,
-        etc.
+        This form is intended as a way to request additional functionality for existing resources, data sources, or the provider itself. This may include requests such as adding additional arguments or attributes enabled by upstream API changes, additional validation for arguments, etc.
 
-        If the absense of the requested feature is causing unexpected behavior
-        in the provider, the "Report a Bug" form should be used. For entirely
-        new resources, data sources, or services, please use the Request a "New
-        Resource or Data Source" form.
+        If the absense of the requested feature is causing unexpected behavior in the provider, the "Report a Bug" form should be used. For entirely new resources, data sources, or services, please use the Request a "New Resource or Data Source" form.
 
   - type: textarea
     id: description
@@ -43,14 +36,9 @@ body:
     attributes:
       label: Potential Terraform Configuration
       description: |
-        If this request was implemented, what might the Terraform configuration
-        look like? A best guess is helpful, even if you're unsure of exactly
-        what the end result will look like. This helps maintainers and the
-        community better understand how you (someone who is in need of this
-        feature) envisions it.
+        If this request was implemented, what might the Terraform configuration look like? A best guess is helpful, even if you're unsure of exactly what the end result will look like. This helps maintainers and the community better understand how you (someone who is in need of this feature) envisions it.
 
-        **Note:** This field will render in HCL, so there is no need to add a
-        [code fence](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks).
+        **Note:** This field will render in HCL, so there is no need to add a [code fence](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks).
       render: terraform
     validations:
       required: false
@@ -60,9 +48,7 @@ body:
     attributes:
       label: References
       description: |
-        Where possible, please supply links to Vault documentation, other
-        GitHub issues (open or closed) or pull requests that give additional
-        context.
+        Where possible, please supply links to Vault documentation, other GitHub issues (open or closed) or pull requests that give additional context.
 
         [Information about referencing Github Issues](https://help.github.com/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests)
     validations:
@@ -73,11 +59,7 @@ body:
     attributes:
       label: Would you like to implement a fix?
       description: |
-        If you plan to implement a fix for this, check this box to let the
-        maintainers and community know (you can update this later if you change
-        your mind). If this would be your first contribution, refer to
-        [Developing the Provider](https://github.com/hashicorp/terraform-provider-vault#developing-the-provider)
-        for tips on getting started.
+        If you plan to implement a fix for this, check this box to let the maintainers and community know (you can update this later if you change your mind). If this would be your first contribution, refer to [Developing the Provider](https://github.com/hashicorp/terraform-provider-vault#developing-the-provider) for tips on getting started.
       options:
         - "No"
         - "Yes"