Skip to content
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

fix(secret): corrects the corresponding find functor #301

Merged
merged 1 commit into from
May 11, 2024

Conversation

RomilShah
Copy link
Contributor

@RomilShah RomilShah commented May 10, 2024

Description

Due to a recent refactor in the v2 client library,
the list secrets function now returns the entire
secret objects instead of just reading the metadata
in the previous implementation. This changed object
altogther and the way other sections of code fetched
the secret name.

This commit addresses the issue by correcting the
find functions and other methods where secret name is
referred to.

@RomilShah RomilShah requested review from a team as code owners May 10, 2024 12:23
Copy link

🤖 Pull Request Artifacts (#9032163504) 🎉

@pallabpain pallabpain changed the title 🔧 fix(secrets): resolves creation of v2 secrets fix(secrets): resolves creation of v2 secrets May 10, 2024
@pallabpain pallabpain changed the title fix(secrets): resolves creation of v2 secrets fix(secret): resolves creation of v2 secrets May 10, 2024
@pallabpain pallabpain changed the title fix(secret): resolves creation of v2 secrets fix(secret): corrects the corresponding find functor May 10, 2024
Copy link
Member

@pallabpain pallabpain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please update the commit body with the description of the issue and the solution this commit provides. It's good to have the context in the commit message.

Copy link

🤖 Pull Request Artifacts (#9032932555) 🎉

Due to a recent refactor in the v2 client library,
the list secrets function now returns the entire
secret objects instead of just reading the metadata
in the previous implementation. This changed object
altogther and the way other sections of code fetched
the secret name.

This commit addresses the issue by correcting the
find functions and other methods where secret name is
referred to.
Copy link

🤖 Pull Request Artifacts (#9044380473) 🎉

@pallabpain pallabpain added the 🐛 bug Something isn't working label May 11, 2024
@pallabpain pallabpain merged commit 41e287b into devel May 11, 2024
6 checks passed
rr-github-ci-user pushed a commit that referenced this pull request May 16, 2024
# [7.4.0](v7.3.3...v7.4.0) (2024-05-16)

### Bug Fixes

* **configtree:** handle project-level trees correctly in commit sub-command ([6899711](6899711))
* **configtree:** replace --project with --organization flag ([ab3e5ca](ab3e5ca))
* corrects the with_org usage ([29d4ae4](29d4ae4))
* **secret:** corrects corresponding find functions ([#301](#301)) ([41e287b](41e287b))

### Features

* **configtree:** add support for key-level Metadata ([5b7c1bb](5b7c1bb))
* **configtrees:** add support for interacting with Config trees ([f979128](f979128))
* **configtree:** support exporting YAML files in `import` command ([f7f145f](f7f145f))
* **graph:** add support for Graphviz ([760d6c0](760d6c0))
* **state:** implement StateFile to store intermediate state ([3302133](3302133))
* **vpn:** add support for registering machine for Android or iOS ([c385bea](c385bea))
@rr-github-ci-user
Copy link
Collaborator

🎉 This PR is included in version 7.4.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@ankitrgadiya ankitrgadiya deleted the fix/v2_secret branch May 28, 2024 06:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working released
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants