st2kv : Non-hexadecimal digit found
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
STACKSTORM VERSION
Paste the output of st2 --version: v3.9dev (Ubuntu 20.04.6 LTS GNU/Linux x86_64)
OS, environment, install method
Docker
Steps to reproduce the problem
In v3.9dev, I tried to store a key with an encrypted value. The encrypted value contains special characters (., -, _)
When I use st2kv in my config file, Stackstorm asks me: 'Non-hexadecimal digit found'. But it's OK with version v3.8.
commands :
st2 key set my_token 'my.fake-super_password' --encrypt
The config file:
---
connections:
my_token: "{{st2kv.system.my_token | decrypt_kv}}"
url: "my_api.com"
Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the st2 key set my_token ... --encrypt command and the st2kv.system.my_token | decrypt_kv configuration path. Reproduce the failure with the supplied value, then compare the v3.9dev behavior with v3.8. Done means encrypted values containing ., -, or _ work in the configuration without the non-hexadecimal-digit error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100