Type interfaces describing spec and state are really messy right now
- deploy/type.ts describes v1 spec and provisioner state objects
- lexicon/lightning describes provisioner state
- lexicon/portability.d.ts describes v2 spec
- Also some complication around the v2 state yaml files
What we need is:
- as few type interfaces as possible. Maybe the deploy types can just alias out the provisioner namespace?
- A user and AI guide to explain how to make changes
I'd also love a common dependency between kit and lightning, to help keep both repos honest.
Type interfaces describing spec and state are really messy right now
What we need is:
I'd also love a common dependency between kit and lightning, to help keep both repos honest.