The old version of Sputnik had the concept of "defaults" for defining Device Types, Blueprints, GG functions, etc, but it was tightly coupled to core stack and deployed along with it.
Ideally rather than "defaults" then would just be additional stack to define and deploy the metadata (Device Types, Blueprints, etc) and the lambda code to support them "as code", in an on-going fashion. Rather than an initial single deployment of adding this functionality to the service, it would be seen an codified implementation of the resources to define the specific use case that is used instead of the UI, and is preferred production grade example.
We need to completely re-architect the way we handle this and refactor existing examples into this new system.
Currently "defaults / examples" have been removed from the beta release until we do this refactor.
The old version of Sputnik had the concept of "defaults" for defining Device Types, Blueprints, GG functions, etc, but it was tightly coupled to core stack and deployed along with it.
Ideally rather than "defaults" then would just be additional stack to define and deploy the metadata (Device Types, Blueprints, etc) and the lambda code to support them "as code", in an on-going fashion. Rather than an initial single deployment of adding this functionality to the service, it would be seen an codified implementation of the resources to define the specific use case that is used instead of the UI, and is preferred production grade example.
We need to completely re-architect the way we handle this and refactor existing examples into this new system.