backport of commit ba647ca

Author: fairclothjm

.changes/0.14.1.md

@@ -18,16 +18,3 @@ How was this change implemented?
 [Example](https://github.com/hashicorp/vault/commit/2715f5cec982aabc7b7a6ae878c547f6f475bba6)
 [ ] Add output for any tests not ran in CI to the PR description (eg, acceptance tests)
 [ ] Backwards compatible
-[ ] Changelog entry added. See [Updating the Changelog](https://github.com/hashicorp/vault-plugin-database-snowflake/blob/main/README.md#updating-the-changelog).
-
-## PCI review checklist
-
-<!-- heimdall_github_prtemplate:grc-pci_dss-2024-01-05 -->
-
-- [ ] I have documented a clear reason for, and description of, the change I am making.
-
-- [ ] If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
-
-- [ ] If applicable, I've documented the impact of any changes to security controls.
-
-  Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

.changes/unreleased/.gitkeep

@@ -46,7 +46,6 @@ Temporary Items
 vault-plugin-database-snowflake
 bin/
 pkg/
-scripts/custom/
 
 .idea/
 # End of https://www.gitignore.io/api/go,macos

.changes/unreleased/BUG FIXES-20250911-121401.yaml

@@ -1,23 +1,11 @@
-## 0.14.1
-### June 5, 2025
+## Unreleased
 
-IMPROVEMENTS:
-
-* Added key-pair auth support for database configuration in Vault 1.20.x (https://github.com/hashicorp/vault-plugin-database-snowflake/pull/116)
-
-## 0.14.0
-### May 23, 2025
-
-IMPROVEMENTS:
-
-* Updated dependencies (https://github.com/hashicorp/vault-plugin-database-snowflake/pull/105)
-
-## 0.13.2
-### June 5, 2025
+## 0.13.1
+### May 28, 2025
 
 IMPROVEMENTS:
 
-* Added key-pair auth support for database configuration in Vault 1.19.6 (https://github.com/hashicorp/vault-plugin-database-snowflake/pull/117)
+* Updated dependencies (https://github.com/hashicorp/vault-plugin-database-snowflake/pull/114)
 
 ## 0.13.0
 ### Feb 11, 2025
@@ -26,26 +14,12 @@ IMPROVEMENTS:
 
 * Updated dependencies (https://github.com/hashicorp/vault-plugin-database-snowflake/pull/100)
 
-## 0.12.2
-### June 5, 2025
-
-IMPROVEMENTS:
-
-* Added key-pair auth support for database configuration in Vault 1.18.11 Enterprise (https://github.com/hashicorp/vault-plugin-database-snowflake/pull/118)
-
 ## 0.12.0
 ### Sept 4, 2024
 
 IMPROVEMENTS:
 * Updated dependencies (https://github.com/hashicorp/vault-plugin-database-snowflake/pull/92)
 
-## 0.11.2
-### June 5, 2025
-
-IMPROVEMENTS:
-
-* Added key-pair auth support for database configuration in Vault 1.17.18 Enterprise (https://github.com/hashicorp/vault-plugin-database-snowflake/pull/119)
-
 ## 0.11.0
 ### May 20, 2024
 
@@ -56,13 +30,6 @@ IMPROVEMENTS:
   * `github.com/jackc/pgx/v4` v4.18.1 -> v4.18.2
   * `github.com/snowflakedb/gosnowflake` v1.7.2 -> v1.8.0
 
-## 0.10.3
-### June 5, 2025
-
-IMPROVEMENTS:
-
-* Added key-pair auth support for database configuration in Vault 1.16.22 Enterprise (https://github.com/hashicorp/vault-plugin-database-snowflake/pull/120)
-
 ## 0.10.0
 ### Jan 31, 2024
 CHANGES:

.changie.yaml

@@ -4,8 +4,6 @@ VETARGS?=-asmdecl -atomic -bool -buildtags -copylocks -methods -nilfunc -printf
 EXTERNAL_TOOLS=
 BUILD_TAGS?=${TOOL}
 GOFMT_FILES?=$$(find . -name '*.go')
-PLUGIN_NAME := $(shell command ls cmd/)
-PLUGIN_DIR ?= $$GOPATH/vault-plugins
 
 default: dev
 
@@ -49,12 +47,4 @@ fmtcheck:
 fmt:
 	gofmt -w $(GOFMT_FILES)
 
-configure: dev
-	./bootstrap/configure.sh \
-	$(PLUGIN_DIR) \
-	$(PLUGIN_NAME) \
-	$(CONNECTION_URL) \
-	$(PRIVATE_KEY) \
-	$(SNOWFLAKE_USERNAME)
-
 .PHONY: bin default generate test vet bootstrap fmt fmtcheck

.github/PULL_REQUEST_TEMPLATE.md

@@ -27,28 +27,6 @@ Feature requests can be submitted in the Issues section as well.
 If you believe you have found a security issue in Vault or with this plugin, _please 
 responsibly disclose_ by contacting HashiCorp at [security@hashicorp.com](mailto:security@hashicorp.com).
 
-### Configure Plugin
-
-A [scripted configuration](bootstrap/configure.sh) of the plugin is provided in
-this repository. You can use the script or manually configure the secrets engine
-using documentation.
-
-To apply the scripted configuration, run the `make configure` target to
-register, enable, and configure the plugin with your local Vault instance. You
-can specify the plugin name, plugin directory, mount path, connection URL and
-private key path. Default values for plugin name and directory from the
-Makefile will be used if arguments aren't provided.
-
-```sh
-$ PLUGIN_NAME=vault-plugin-database-snowflake \
-  PLUGIN_DIR=$GOPATH/vault-plugins \
-  CONNECTION_URL=foo.snowflakecomputing.com/BAR \
-  PRIVATE_KEY=/path/to/private/key/file \
-  SNOWFLAKE_USERNAME=user1 \
-  make configure
-```
-
-
 ## Acceptance Testing
 
 In order to perform acceptance testing, you need to set the environment variable `VAULT_ACC=1` 
@@ -71,42 +49,3 @@ To run the acceptance tests, invoke `make testacc`:
 ```sh
 $ make testacc
 ```
-
-## Updating the Changelog
-
-All pull requests that introduce a user-facing change must include a changelog
-entry. We use the [changie](https://changie.dev/) tool to manage these entries
-and automate the release process.
-
----
-### 1. Installing Changie
-
-You only need to do this once. If you don't have `changie` installed, choose one of the options below.
-
-* **Homebrew** (macOS):
-    ```shell
-    brew install changie
-    ```
-* **Go Install**:
-    ```shell
-    go install github.com/miniscruff/changie@latest
-    ```
-* **Other Methods**:
-  See the [official changie installation guide](https://changie.dev/guide/installation/) for other options, including pre-compiled binaries.
-
----
-### 2. Creating an Entry
-
-Once your code changes are complete, create the changelog entry:
-
-1.  **Run the command** in your terminal:
-    ```shell
-    changie new
-    ```
-2.  **Follow the prompts.** An interactive prompt will ask you to select the
-    kind of change (e.g., `BREAKING CHANGES`, `NOTES`, `FEATURES`) and write a concise description of
-    what you changed.
-
-3.  **Commit the new file.** After you're done, `changie` will create a new
-    YAML file in the `.changie/unreleased` directory. Commit this file along with your other
-    code changes before submitting your pull request.