Closed lgalabru closed 1 year ago
This is fantastic. Would be really helpful for "private" testnet scenarios or even just a public "mocknet".
There is a gap between local devnet and public testnet. Public testnet is great for testing an app/protocol in as realistic an environment as possible, but it has inconsistent block times and generally isn't great for just exposing an app to testers for iterative development. Something like this would be the perfect fit.
Related: #973
Should we convert to epic (and enable epics on the repo/board)? cc @smcclellan
@MicaiahReid All "known steps" in the OC are checked; can we close this? Is any remaining work ticketed?
@smcclellan most issues are now being tracked at the actual Stacks Devnet API repo, but there's one more PR open here on the clarinet side to merge my changes to clarinet back into master (so we'll no longer have a separate fork).
It's nearing the end of its review, then we should be able to close this issue. I've added this last PR as a task here on this issue.
All Clarinet-related tasks for the devnet service should be completed! Closing.
Phase 1: Proof of concept
clarinet integrate --k8s
can spin up a devnet network on a local K8S cluster (instead of docker).Phase 2: New stacks-devnet-api component
Architecture
stacks-devnet-api
:networks
, via a REST API (described above), by issuing k8s commands.stacks-network
:Endpoints
Create a network
Body
Response
Get network informations
Manage a network
Commands available:
HTTP Requests forwarding
...
Delete a network
Note: spec is under-specified at the moment, @MicaiahReid will take the lead on this project and share his exploration with the team. Related: https://github.com/hirosystems/artemis/issues/446
Current known steps: