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.
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:
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.