fix(hashicorp): Incorrect work with json in vault code

[00041275]

Incorrect work with json. The json logic for secret_value should be similar to that of secret manager

This problem not have issue .

✅ Checks

• My pull request adheres to the code style of this project
• I have updated the documentation as required

After making the change, my keephq, which stores secrets in vault, began to work well

close #2927

[vercel]

@00041275 is attempting to deploy a commit to the KeepHQ Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[talboren]

@00041275 thank you for this PR! can you explain what's not working? maybe you can create an issue for that?

[talboren]

@00041275 ping :)

[00041275]

of the Team first ne

sorry for waiting.
The fact is that when creating the provider, the script vault received json, but in the case of creating the API it was just a string. This broke the entire keephq initialization. I couldn't understand the reason. As a result, having studied similar implementations on Google, Amazon realized that it is impossible to convert data into json unambiguously when recording. That's the whole point why i rewrite row with json.loads.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
keep	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 30, 2024 9:31am

[talboren]

@00041275 if I understand correctly, you are referring to API key? Have you had a chance to test your fix? is it working properly now? would love to chat more in our Slack if you're not in it already

[00041275]

@00041275 if I understand correctly, you are referring to API key? Have you had a chance to test your fix? is it working properly now? would love to chat more in our Slack if you're not in it already

Yes, that's right, this is an API key. Of course, everything works for me with the change. I'm not on Slack.

[talboren]

LGTM!

[talboren]

@00041275 if I understand correctly, you are referring to API key? Have you had a chance to test your fix? is it working properly now? would love to chat more in our Slack if you're not in it already

Yes, that's right, this is an API key. Of course, everything works for me with the change. I'm not on Slack.

Would love for you to join @00041275 :) LGTM'd and merging as soon as workflows pass!

[github-actions]

🔥 Fantastic work @00041275! Your very first PR to keep has been merged! 🎉🥳

You've just taken your first step into open-source, and we couldn't be happier to have you onboard. 🙌
If you're feeling adventurous, why not dive into another issue and keep contributing? The community would love to see more from you! 🚀

For any support, feel free to reach out on the community: https://slack.keephq.dev. Happy coding! 👩‍💻👨‍💻

[00041275]

ЛГТМ!

Thanks)