oasisprotocol / oasisprotocol/oasis-sdk
Support non-encrypted variables in ROFL manifest yaml
A pull request for this has already been merged.
- #2481 by @martintomazic — merged
- Dominant language
- Rust
- Stars
- 90
- Forks
- 35
- Avg merge
- 5d 9h
- Merged PRs (30d)
- 5
Description
Currently, there are two ways to configure your ROFL:
- define secrets in rofl.yaml which are fed to your docker image
- define publicly visible variables in
compose.yaml,Dockerfile, or the image itself
Step 2. will produce a different enclave ID for different configuration every build which is annoying since it's still the same (audited) app. Add support for defining publicly exposed variables to rofl.yaml. They should work exactly the same as secrets, just that they are unencrypted.
Rough TODO:
- cli: Similar to
secretsadd anotherenvironmentsection torofl.yamldeployment. - cli: Similar to
oasis rofl secretaddoasis rofl environmentcmd (aliasenv) - cli: Make sure there are no name collisions with secrets.
- explorer: Add support to Explorer
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 reviewing the existing secrets flow in rofl.yaml and the oasis rofl secret command, then inspect the closed pull request #2481 for related work. Done means publicly exposed variables are supported in the deployment manifest and CLI, do not collide with secrets, and are also supported by Explorer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100