oasisprotocol / oasisprotocol/cli
`rofl deploy`: Check, if resources are satisfied by the offer
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 80
- Forks
- 23
- Avg merge
- 9h 43m
- Merged PRs (30d)
- 3
Description
If no --offer provided, it currently selects the first offer on the list (the most recent one). If TEE kind and resources (disk, memory, storage) in rofl.yaml aren't satisfied with the offer, it should skip to the next one until all resources are satisfied.
Keep in mind that the required storage is the specified resources.storage.size in the manifest + an additional 2GB for the oasis-boot image.
If an offer is explicitly selected, return error, if the resources are not satisfied. Pass -f to override the error.
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 at the rofl deploy command and trace how it selects offers and reads rofl.yaml. Verify TEE kind, disk, memory, and storage requirements, including the extra 2GB for the oasis-boot image. Done means automatic selection skips insufficient offers, while explicit --offer errors unless -f overrides it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100