feat(parametermanager): add support for gcp parameter manager service#3699
Conversation
f5db654 to
aa4c9d7
Compare
|
I tried running the integration tests and they came back with some errors. Could you please take a look? |
Could you please try building the project using |
I have done this, but I'm still getting the error. |
I've created #3979 as a copy of this PR, to trigger ITs. |
Still shows errors in integration tests (e.g. https://github.com/GoogleCloudPlatform/spring-cloud-gcp/actions/runs/16457637114/job/46518308602?pr=3979) |
This module is the same as the Secret Manager module. Since the PR for regional support in Secret Manager has been merged, this PR needs to be updated accordingly. I will let you know once it's done |
|
@jinseopkim0 I've updated the PR. Please take a look. |
Thanks, confirmed integration tests are passing in #3979. |
🤖 I have created a release *beep* *boop* --- ## [7.3.0](v7.2.0...v7.3.0) (2025-08-29) ### Features * **parametermanager:** add support for gcp parameter manager service ([#3699](#3699)) ([c0748f1](c0748f1)) ### Bug Fixes * **deps:** update dependency com.google.cloud:libraries-bom to v26.67.0 ([#4104](#4104)) ([e8aec00](e8aec00)) * **deps:** update gapic-generator-java-bom.version to v2.62.0 ([#4099](#4099)) ([8a91c2c](8a91c2c)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
…#3699) Issue: [#3698](#3698) **Description** This pull request introduces a feature to the Spring Cloud GCP library, adding support for the parameter manager module. This enhancement enables the library to resolve the parameter presented in GCP Parameter Manager in the `application.properties` file and using the `@Value` annotation. It also expose the CRUD methods for the Parameter Manager. It will be implemented the same way as `secretmanager` is implemented. **Proposed Changes:** - Add the support of `parametermanager` module in the s`pring-cloud-gcp` which provides below functionality. - Inject parameter from Parameter Manager using `@Value` annotation with specified path i.e `pm@pm@global/my-param/v1` - Resolve the parameter from the Parameter Manager specified in the `application.properties` file - Expose the methods for `createParameter`, `enableParameterVersion`, `disableParameterVersion`, `deleteParameterVersion`, `getParameterString`, `deleteParameter`, `renderedParameterVersionString` - Add sample application which uses `parametermanager` to showcase the usecases - Add the documentation to reflect the new capabilities of `parametermanager` Refer to the [parametermanager.adoc](https://github.com/GoogleCloudPlatform/spring-cloud-gcp/blob/2aecef8378274397ee667dd1a9fbcf72da43355d/docs/src/main/asciidoc/parametermanager.adoc) file for detailed documentation. Performed the below mentioned manual unit tests to validate the working of the global and regional parameter operations. * Create parameter with given location, parameterId, version and payload * Create parameter with given project, location, parameterId, version and payload * Create parameter with given location, parameterId, version and payload, format * Create parameter with given project, location, parameterId, version and payload, format * Create parameter with given location, parameterId, version and payload and invalid projectId (project on which user doesn't have access) * Enable parameter version with given location, parameterId and version * Enable parameter version with given project, location, parameterId and version * Disable parameter version with given location, parameterId and version * Disable parameter version with given project, location, parameterId and version * Delete parameter with location and parameterId * Delete parameter with project, location and parameterId * Delete parameter version with location, parameterId and version * Delete parameter version with project, location, parameterId and version * Check if parameter exist with location and parameterId * Check if parameter exist with project, location and parameterId * Check if parameter version exist with location, parameterId and version * Check if parameter version exist with project, location, parameterId and version * Read parameter with parameter Identifier * Render parameter with parameter Identifier * Inject with `@value` annotation * Read parameter with project, location, parameterId and version for other project using service account * Check parameter resolution mentioned in the `application.properties`. More information about parameter manager: https://cloud.google.com/secret-manager/parameter-manager/docs/overview
…#3699) Issue: [#3698](#3698) **Description** This pull request introduces a feature to the Spring Cloud GCP library, adding support for the parameter manager module. This enhancement enables the library to resolve the parameter presented in GCP Parameter Manager in the `application.properties` file and using the `@Value` annotation. It also expose the CRUD methods for the Parameter Manager. It will be implemented the same way as `secretmanager` is implemented. **Proposed Changes:** - Add the support of `parametermanager` module in the s`pring-cloud-gcp` which provides below functionality. - Inject parameter from Parameter Manager using `@Value` annotation with specified path i.e `pm@pm@global/my-param/v1` - Resolve the parameter from the Parameter Manager specified in the `application.properties` file - Expose the methods for `createParameter`, `enableParameterVersion`, `disableParameterVersion`, `deleteParameterVersion`, `getParameterString`, `deleteParameter`, `renderedParameterVersionString` - Add sample application which uses `parametermanager` to showcase the usecases - Add the documentation to reflect the new capabilities of `parametermanager` Refer to the [parametermanager.adoc](https://github.com/GoogleCloudPlatform/spring-cloud-gcp/blob/2aecef8378274397ee667dd1a9fbcf72da43355d/docs/src/main/asciidoc/parametermanager.adoc) file for detailed documentation. Performed the below mentioned manual unit tests to validate the working of the global and regional parameter operations. * Create parameter with given location, parameterId, version and payload * Create parameter with given project, location, parameterId, version and payload * Create parameter with given location, parameterId, version and payload, format * Create parameter with given project, location, parameterId, version and payload, format * Create parameter with given location, parameterId, version and payload and invalid projectId (project on which user doesn't have access) * Enable parameter version with given location, parameterId and version * Enable parameter version with given project, location, parameterId and version * Disable parameter version with given location, parameterId and version * Disable parameter version with given project, location, parameterId and version * Delete parameter with location and parameterId * Delete parameter with project, location and parameterId * Delete parameter version with location, parameterId and version * Delete parameter version with project, location, parameterId and version * Check if parameter exist with location and parameterId * Check if parameter exist with project, location and parameterId * Check if parameter version exist with location, parameterId and version * Check if parameter version exist with project, location, parameterId and version * Read parameter with parameter Identifier * Render parameter with parameter Identifier * Inject with `@value` annotation * Read parameter with project, location, parameterId and version for other project using service account * Check parameter resolution mentioned in the `application.properties`. More information about parameter manager: https://cloud.google.com/secret-manager/parameter-manager/docs/overview
…#3699) Issue: [#3698](#3698) **Description** This pull request introduces a feature to the Spring Cloud GCP library, adding support for the parameter manager module. This enhancement enables the library to resolve the parameter presented in GCP Parameter Manager in the `application.properties` file and using the `@Value` annotation. It also expose the CRUD methods for the Parameter Manager. It will be implemented the same way as `secretmanager` is implemented. **Proposed Changes:** - Add the support of `parametermanager` module in the s`pring-cloud-gcp` which provides below functionality. - Inject parameter from Parameter Manager using `@Value` annotation with specified path i.e `pm@pm@global/my-param/v1` - Resolve the parameter from the Parameter Manager specified in the `application.properties` file - Expose the methods for `createParameter`, `enableParameterVersion`, `disableParameterVersion`, `deleteParameterVersion`, `getParameterString`, `deleteParameter`, `renderedParameterVersionString` - Add sample application which uses `parametermanager` to showcase the usecases - Add the documentation to reflect the new capabilities of `parametermanager` Refer to the [parametermanager.adoc](https://github.com/GoogleCloudPlatform/spring-cloud-gcp/blob/2aecef8378274397ee667dd1a9fbcf72da43355d/docs/src/main/asciidoc/parametermanager.adoc) file for detailed documentation. Performed the below mentioned manual unit tests to validate the working of the global and regional parameter operations. * Create parameter with given location, parameterId, version and payload * Create parameter with given project, location, parameterId, version and payload * Create parameter with given location, parameterId, version and payload, format * Create parameter with given project, location, parameterId, version and payload, format * Create parameter with given location, parameterId, version and payload and invalid projectId (project on which user doesn't have access) * Enable parameter version with given location, parameterId and version * Enable parameter version with given project, location, parameterId and version * Disable parameter version with given location, parameterId and version * Disable parameter version with given project, location, parameterId and version * Delete parameter with location and parameterId * Delete parameter with project, location and parameterId * Delete parameter version with location, parameterId and version * Delete parameter version with project, location, parameterId and version * Check if parameter exist with location and parameterId * Check if parameter exist with project, location and parameterId * Check if parameter version exist with location, parameterId and version * Check if parameter version exist with project, location, parameterId and version * Read parameter with parameter Identifier * Render parameter with parameter Identifier * Inject with `@value` annotation * Read parameter with project, location, parameterId and version for other project using service account * Check parameter resolution mentioned in the `application.properties`. More information about parameter manager: https://cloud.google.com/secret-manager/parameter-manager/docs/overview
…#3699) Issue: [#3698](#3698) **Description** This pull request introduces a feature to the Spring Cloud GCP library, adding support for the parameter manager module. This enhancement enables the library to resolve the parameter presented in GCP Parameter Manager in the `application.properties` file and using the `@Value` annotation. It also expose the CRUD methods for the Parameter Manager. It will be implemented the same way as `secretmanager` is implemented. **Proposed Changes:** - Add the support of `parametermanager` module in the s`pring-cloud-gcp` which provides below functionality. - Inject parameter from Parameter Manager using `@Value` annotation with specified path i.e `pm@pm@global/my-param/v1` - Resolve the parameter from the Parameter Manager specified in the `application.properties` file - Expose the methods for `createParameter`, `enableParameterVersion`, `disableParameterVersion`, `deleteParameterVersion`, `getParameterString`, `deleteParameter`, `renderedParameterVersionString` - Add sample application which uses `parametermanager` to showcase the usecases - Add the documentation to reflect the new capabilities of `parametermanager` Refer to the [parametermanager.adoc](https://github.com/GoogleCloudPlatform/spring-cloud-gcp/blob/2aecef8378274397ee667dd1a9fbcf72da43355d/docs/src/main/asciidoc/parametermanager.adoc) file for detailed documentation. Performed the below mentioned manual unit tests to validate the working of the global and regional parameter operations. * Create parameter with given location, parameterId, version and payload * Create parameter with given project, location, parameterId, version and payload * Create parameter with given location, parameterId, version and payload, format * Create parameter with given project, location, parameterId, version and payload, format * Create parameter with given location, parameterId, version and payload and invalid projectId (project on which user doesn't have access) * Enable parameter version with given location, parameterId and version * Enable parameter version with given project, location, parameterId and version * Disable parameter version with given location, parameterId and version * Disable parameter version with given project, location, parameterId and version * Delete parameter with location and parameterId * Delete parameter with project, location and parameterId * Delete parameter version with location, parameterId and version * Delete parameter version with project, location, parameterId and version * Check if parameter exist with location and parameterId * Check if parameter exist with project, location and parameterId * Check if parameter version exist with location, parameterId and version * Check if parameter version exist with project, location, parameterId and version * Read parameter with parameter Identifier * Render parameter with parameter Identifier * Inject with `@value` annotation * Read parameter with project, location, parameterId and version for other project using service account * Check parameter resolution mentioned in the `application.properties`. More information about parameter manager: https://cloud.google.com/secret-manager/parameter-manager/docs/overview
…#3699) Issue: [#3698](#3698) **Description** This pull request introduces a feature to the Spring Cloud GCP library, adding support for the parameter manager module. This enhancement enables the library to resolve the parameter presented in GCP Parameter Manager in the `application.properties` file and using the `@Value` annotation. It also expose the CRUD methods for the Parameter Manager. It will be implemented the same way as `secretmanager` is implemented. **Proposed Changes:** - Add the support of `parametermanager` module in the s`pring-cloud-gcp` which provides below functionality. - Inject parameter from Parameter Manager using `@Value` annotation with specified path i.e `pm@pm@global/my-param/v1` - Resolve the parameter from the Parameter Manager specified in the `application.properties` file - Expose the methods for `createParameter`, `enableParameterVersion`, `disableParameterVersion`, `deleteParameterVersion`, `getParameterString`, `deleteParameter`, `renderedParameterVersionString` - Add sample application which uses `parametermanager` to showcase the usecases - Add the documentation to reflect the new capabilities of `parametermanager` Refer to the [parametermanager.adoc](https://github.com/GoogleCloudPlatform/spring-cloud-gcp/blob/2aecef8378274397ee667dd1a9fbcf72da43355d/docs/src/main/asciidoc/parametermanager.adoc) file for detailed documentation. Performed the below mentioned manual unit tests to validate the working of the global and regional parameter operations. * Create parameter with given location, parameterId, version and payload * Create parameter with given project, location, parameterId, version and payload * Create parameter with given location, parameterId, version and payload, format * Create parameter with given project, location, parameterId, version and payload, format * Create parameter with given location, parameterId, version and payload and invalid projectId (project on which user doesn't have access) * Enable parameter version with given location, parameterId and version * Enable parameter version with given project, location, parameterId and version * Disable parameter version with given location, parameterId and version * Disable parameter version with given project, location, parameterId and version * Delete parameter with location and parameterId * Delete parameter with project, location and parameterId * Delete parameter version with location, parameterId and version * Delete parameter version with project, location, parameterId and version * Check if parameter exist with location and parameterId * Check if parameter exist with project, location and parameterId * Check if parameter version exist with location, parameterId and version * Check if parameter version exist with project, location, parameterId and version * Read parameter with parameter Identifier * Render parameter with parameter Identifier * Inject with `@value` annotation * Read parameter with project, location, parameterId and version for other project using service account * Check parameter resolution mentioned in the `application.properties`. More information about parameter manager: https://cloud.google.com/secret-manager/parameter-manager/docs/overview
…#3699) Issue: [#3698](#3698) **Description** This pull request introduces a feature to the Spring Cloud GCP library, adding support for the parameter manager module. This enhancement enables the library to resolve the parameter presented in GCP Parameter Manager in the `application.properties` file and using the `@Value` annotation. It also expose the CRUD methods for the Parameter Manager. It will be implemented the same way as `secretmanager` is implemented. **Proposed Changes:** - Add the support of `parametermanager` module in the s`pring-cloud-gcp` which provides below functionality. - Inject parameter from Parameter Manager using `@Value` annotation with specified path i.e `pm@pm@global/my-param/v1` - Resolve the parameter from the Parameter Manager specified in the `application.properties` file - Expose the methods for `createParameter`, `enableParameterVersion`, `disableParameterVersion`, `deleteParameterVersion`, `getParameterString`, `deleteParameter`, `renderedParameterVersionString` - Add sample application which uses `parametermanager` to showcase the usecases - Add the documentation to reflect the new capabilities of `parametermanager` Refer to the [parametermanager.adoc](https://github.com/GoogleCloudPlatform/spring-cloud-gcp/blob/2aecef8378274397ee667dd1a9fbcf72da43355d/docs/src/main/asciidoc/parametermanager.adoc) file for detailed documentation. Performed the below mentioned manual unit tests to validate the working of the global and regional parameter operations. * Create parameter with given location, parameterId, version and payload * Create parameter with given project, location, parameterId, version and payload * Create parameter with given location, parameterId, version and payload, format * Create parameter with given project, location, parameterId, version and payload, format * Create parameter with given location, parameterId, version and payload and invalid projectId (project on which user doesn't have access) * Enable parameter version with given location, parameterId and version * Enable parameter version with given project, location, parameterId and version * Disable parameter version with given location, parameterId and version * Disable parameter version with given project, location, parameterId and version * Delete parameter with location and parameterId * Delete parameter with project, location and parameterId * Delete parameter version with location, parameterId and version * Delete parameter version with project, location, parameterId and version * Check if parameter exist with location and parameterId * Check if parameter exist with project, location and parameterId * Check if parameter version exist with location, parameterId and version * Check if parameter version exist with project, location, parameterId and version * Read parameter with parameter Identifier * Render parameter with parameter Identifier * Inject with `@value` annotation * Read parameter with project, location, parameterId and version for other project using service account * Check parameter resolution mentioned in the `application.properties`. More information about parameter manager: https://cloud.google.com/secret-manager/parameter-manager/docs/overview
…#3699) Issue: [#3698](#3698) **Description** This pull request introduces a feature to the Spring Cloud GCP library, adding support for the parameter manager module. This enhancement enables the library to resolve the parameter presented in GCP Parameter Manager in the `application.properties` file and using the `@Value` annotation. It also expose the CRUD methods for the Parameter Manager. It will be implemented the same way as `secretmanager` is implemented. **Proposed Changes:** - Add the support of `parametermanager` module in the s`pring-cloud-gcp` which provides below functionality. - Inject parameter from Parameter Manager using `@Value` annotation with specified path i.e `pm@pm@global/my-param/v1` - Resolve the parameter from the Parameter Manager specified in the `application.properties` file - Expose the methods for `createParameter`, `enableParameterVersion`, `disableParameterVersion`, `deleteParameterVersion`, `getParameterString`, `deleteParameter`, `renderedParameterVersionString` - Add sample application which uses `parametermanager` to showcase the usecases - Add the documentation to reflect the new capabilities of `parametermanager` Refer to the [parametermanager.adoc](https://github.com/GoogleCloudPlatform/spring-cloud-gcp/blob/2aecef8378274397ee667dd1a9fbcf72da43355d/docs/src/main/asciidoc/parametermanager.adoc) file for detailed documentation. Performed the below mentioned manual unit tests to validate the working of the global and regional parameter operations. * Create parameter with given location, parameterId, version and payload * Create parameter with given project, location, parameterId, version and payload * Create parameter with given location, parameterId, version and payload, format * Create parameter with given project, location, parameterId, version and payload, format * Create parameter with given location, parameterId, version and payload and invalid projectId (project on which user doesn't have access) * Enable parameter version with given location, parameterId and version * Enable parameter version with given project, location, parameterId and version * Disable parameter version with given location, parameterId and version * Disable parameter version with given project, location, parameterId and version * Delete parameter with location and parameterId * Delete parameter with project, location and parameterId * Delete parameter version with location, parameterId and version * Delete parameter version with project, location, parameterId and version * Check if parameter exist with location and parameterId * Check if parameter exist with project, location and parameterId * Check if parameter version exist with location, parameterId and version * Check if parameter version exist with project, location, parameterId and version * Read parameter with parameter Identifier * Render parameter with parameter Identifier * Inject with `@value` annotation * Read parameter with project, location, parameterId and version for other project using service account * Check parameter resolution mentioned in the `application.properties`. More information about parameter manager: https://cloud.google.com/secret-manager/parameter-manager/docs/overview
…#3699) Issue: [#3698](#3698) **Description** This pull request introduces a feature to the Spring Cloud GCP library, adding support for the parameter manager module. This enhancement enables the library to resolve the parameter presented in GCP Parameter Manager in the `application.properties` file and using the `@Value` annotation. It also expose the CRUD methods for the Parameter Manager. It will be implemented the same way as `secretmanager` is implemented. **Proposed Changes:** - Add the support of `parametermanager` module in the s`pring-cloud-gcp` which provides below functionality. - Inject parameter from Parameter Manager using `@Value` annotation with specified path i.e `pm@pm@global/my-param/v1` - Resolve the parameter from the Parameter Manager specified in the `application.properties` file - Expose the methods for `createParameter`, `enableParameterVersion`, `disableParameterVersion`, `deleteParameterVersion`, `getParameterString`, `deleteParameter`, `renderedParameterVersionString` - Add sample application which uses `parametermanager` to showcase the usecases - Add the documentation to reflect the new capabilities of `parametermanager` Refer to the [parametermanager.adoc](https://github.com/GoogleCloudPlatform/spring-cloud-gcp/blob/2aecef8378274397ee667dd1a9fbcf72da43355d/docs/src/main/asciidoc/parametermanager.adoc) file for detailed documentation. Performed the below mentioned manual unit tests to validate the working of the global and regional parameter operations. * Create parameter with given location, parameterId, version and payload * Create parameter with given project, location, parameterId, version and payload * Create parameter with given location, parameterId, version and payload, format * Create parameter with given project, location, parameterId, version and payload, format * Create parameter with given location, parameterId, version and payload and invalid projectId (project on which user doesn't have access) * Enable parameter version with given location, parameterId and version * Enable parameter version with given project, location, parameterId and version * Disable parameter version with given location, parameterId and version * Disable parameter version with given project, location, parameterId and version * Delete parameter with location and parameterId * Delete parameter with project, location and parameterId * Delete parameter version with location, parameterId and version * Delete parameter version with project, location, parameterId and version * Check if parameter exist with location and parameterId * Check if parameter exist with project, location and parameterId * Check if parameter version exist with location, parameterId and version * Check if parameter version exist with project, location, parameterId and version * Read parameter with parameter Identifier * Render parameter with parameter Identifier * Inject with `@value` annotation * Read parameter with project, location, parameterId and version for other project using service account * Check parameter resolution mentioned in the `application.properties`. More information about parameter manager: https://cloud.google.com/secret-manager/parameter-manager/docs/overview
…#3699) Issue: [#3698](#3698) **Description** This pull request introduces a feature to the Spring Cloud GCP library, adding support for the parameter manager module. This enhancement enables the library to resolve the parameter presented in GCP Parameter Manager in the `application.properties` file and using the `@Value` annotation. It also expose the CRUD methods for the Parameter Manager. It will be implemented the same way as `secretmanager` is implemented. **Proposed Changes:** - Add the support of `parametermanager` module in the s`pring-cloud-gcp` which provides below functionality. - Inject parameter from Parameter Manager using `@Value` annotation with specified path i.e `pm@pm@global/my-param/v1` - Resolve the parameter from the Parameter Manager specified in the `application.properties` file - Expose the methods for `createParameter`, `enableParameterVersion`, `disableParameterVersion`, `deleteParameterVersion`, `getParameterString`, `deleteParameter`, `renderedParameterVersionString` - Add sample application which uses `parametermanager` to showcase the usecases - Add the documentation to reflect the new capabilities of `parametermanager` Refer to the [parametermanager.adoc](https://github.com/GoogleCloudPlatform/spring-cloud-gcp/blob/2aecef8378274397ee667dd1a9fbcf72da43355d/docs/src/main/asciidoc/parametermanager.adoc) file for detailed documentation. Performed the below mentioned manual unit tests to validate the working of the global and regional parameter operations. * Create parameter with given location, parameterId, version and payload * Create parameter with given project, location, parameterId, version and payload * Create parameter with given location, parameterId, version and payload, format * Create parameter with given project, location, parameterId, version and payload, format * Create parameter with given location, parameterId, version and payload and invalid projectId (project on which user doesn't have access) * Enable parameter version with given location, parameterId and version * Enable parameter version with given project, location, parameterId and version * Disable parameter version with given location, parameterId and version * Disable parameter version with given project, location, parameterId and version * Delete parameter with location and parameterId * Delete parameter with project, location and parameterId * Delete parameter version with location, parameterId and version * Delete parameter version with project, location, parameterId and version * Check if parameter exist with location and parameterId * Check if parameter exist with project, location and parameterId * Check if parameter version exist with location, parameterId and version * Check if parameter version exist with project, location, parameterId and version * Read parameter with parameter Identifier * Render parameter with parameter Identifier * Inject with `@value` annotation * Read parameter with project, location, parameterId and version for other project using service account * Check parameter resolution mentioned in the `application.properties`. More information about parameter manager: https://cloud.google.com/secret-manager/parameter-manager/docs/overview
Backports the following PRs to 6.x: #3699, #3684, #4127 --------- Co-authored-by: suvidha-malaviya <[email protected]>
Issue: #3698
Description
This pull request introduces a feature to the Spring Cloud GCP library, adding support for the parameter manager module. This enhancement enables the library to resolve the parameter presented in GCP Parameter Manager in the
application.propertiesfile and using the@Valueannotation. It also expose the CRUD methods for the Parameter Manager. It will be implemented the same way assecretmanageris implemented.Proposed Changes:
parametermanagermodule in the spring-cloud-gcpwhich provides below functionality.@Valueannotation with specified path i.epm@pm@global/my-param/v1application.propertiesfilecreateParameter,enableParameterVersion,disableParameterVersion,deleteParameterVersion,getParameterString,deleteParameter,renderedParameterVersionStringparametermanagerto showcase the usecasesparametermanagerRefer to the parametermanager.adoc file for detailed documentation.
Performed the below mentioned manual unit tests to validate the working of the global and regional parameter operations.
@valueannotationapplication.properties.More information about parameter manager: https://cloud.google.com/secret-manager/parameter-manager/docs/overview