Support encrypting values in toml tables of pattern [*.secrets]
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 41
- Forks
- 92
- PR merge metrics
- No merged PRs in 30d
Description
In a recent effort to integrate the cipher tool with WSO2 Integrator: ICP, we realized that it is not possible to encrypt values in any [*.secrets] table in a TOML file.
eg:
[icp_server.secrets]
secPassword = "[secret-to-encrypt]"
[icp_server.storage.secrets]
secPassword = "[secret-to-encrypt]"
A Ballerina project, like ICP itself, carries multiple modules. And it requires a structure like the above to allow sub-modules to read the configs they need.
The [secrets] table supported by the cypher tool is accessible only by the default module of a Ballerina project. Therefore, currently, we cannot support secrets in sub-modules.
If the cipher tool supports encrypting values residing in toml tables following the pattern [*.secrets], this issue can be solved.
Contributor guide
No contributing guide indexed for this repository
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 by locating the TOML parsing and existing support for the [secrets] table in the cipher tool. Trace how values are selected for encryption, then verify that nested tables matching [*.secrets] work for the examples in the issue and that existing default-module behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100