Skip to content

chore(deps): update module github.com/ibm/secrets-manager-go-sdk to v2 #160

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 13, 2024

Conversation

terraform-ibm-modules-ops
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
github.com/IBM/secrets-manager-go-sdk require major v1.2.0 -> v2.0.4

Release Notes

IBM/secrets-manager-go-sdk (github.com/IBM/secrets-manager-go-sdk)

v2.0.4

Compare Source

  • Add List filters: secret_types, match_all_labels
  • Add Expiration date field to iam_credentials and service_credentials API responses

v2.0.3

Compare Source

This release adds support fora random password generator policy, allowing you to control the length and complexity of the auto-generated password (numbers, symbols, upper-case).

v2.0.2

Compare Source

This release provides support for a new secret type - Service credentials. Learn more in the service documentation and API Docs.

v2.0.1

Compare Source

This release provides support for retrieving the secret value by using its secret Name. Learn more in the service documentation and API Docs.

v2.0.0

A new version of the Secrets Manager SDKs is now available. The following updates are included in this release.

  • You no longer need to include secret_type in the API URL to identify a secret.
  • The secret group name must be unique per Secrets Manager instance.
  • Resources updates are defined as HTTP patch operations.
  • The configurations API follows the pattern of the Secrets Manager API. config_type acts as the API discriminator, similarly to secret_type.
  • Configurations are modeled as openAPI composites with metadata and data parts, similarly to the Secrets Manager model. Mappings between IAM roles and configurations API follow the same pattern for the Secrets Manager API. For example, an IAM viewer can list configurations to view their metadata.
  • List operations return metadata only for secret, secret version, and config resources.
  • The action to rotate a secret is now the create a new secret version API: POST/v2/secrets/{id}/versions.
  • The action to restore secret version is now the create a new secret version API with the restored_from_version body parameter.
  • The action to delete IAM credentials is now the delete a secret version data API: DELETE /v2/secrets/{id}/versions/{version_id}/secret_data.
  • Policies API is now embedded into the metadata API in version 2.0.
  • The actions to list Secrets and get secret metadata return the versions_total field. The version's content is not included.
  • Current and previous secret versions can be referenced by using the current and previous aliases in version APIs.
  • The secret lock mode names exclusive and exclusive_delete are replaced by remove_previous and remove_previous_and delete. The modes still perform the same action, only the names changed.
    For more information, check out the API docs.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@terraform-ibm-modules-ops
Copy link
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: tests/go.sum
Command failed: mod upgrade --mod-name=github.com/IBM/secrets-manager-go-sdk -t=2
/bin/sh: mod: command not found

@terraform-ibm-modules-ops terraform-ibm-modules-ops force-pushed the renovate/major-ci-dependencies branch 4 times, most recently from 1266bf4 to 2fb6b26 Compare June 8, 2024 15:39
@terraform-ibm-modules-ops terraform-ibm-modules-ops force-pushed the renovate/major-ci-dependencies branch from 2fb6b26 to 6d9deab Compare June 8, 2024 23:33
@ocofaigh
Copy link
Contributor

/run pipeline

@ocofaigh
Copy link
Contributor

Hmm, test failed with:

        	Messages:   	Resource(s) identified to be updated 
        	            	Name: itself
        	            	Address: module.dns.ibm_resource_instance.itself[0]
        	            	Actions: [update]
        	            	DIFF:
        	            	  Before: 
        	            		{"tags":"SECURE_VALUE_HIDDEN_HASH:-8aac7fc1e200266c9dc2bf65e2556cb9a4a2c58d0e83ddd91afdeb2d"}
        	            	  After: 
        	            		{"tags":"SECURE_VALUE_HIDDEN_HASH:-8578ce1590655ead0b946d8e3771121c7ca7f4f8f77b2ad9532783c1"}

Going to retry..

@ocofaigh
Copy link
Contributor

/run pipeline

@ocofaigh ocofaigh merged commit 57eedcf into main Jun 13, 2024
2 checks passed
@ocofaigh ocofaigh deleted the renovate/major-ci-dependencies branch June 13, 2024 12:07
@terraform-ibm-modules-ops
Copy link
Contributor Author

🎉 This PR is included in version 1.6.9 🎉

The release is available on:

Your semantic-release bot 📦🚀

@terraform-ibm-modules-ops
Copy link
Contributor Author

🎉 This PR is included in version 1.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants