-
Notifications
You must be signed in to change notification settings - Fork 952
Description
Describe the issue
Actually I roll out gateways by CI/CD pipeline with file based configuration and pre-configured
- logging via `logs.json´
- access token & connectors via
tb_gateway.json - related connector json configs
To make use of the remote configuration for some gateways, I would like to know:
- if it is possible to provide the gateway with a bootstrap configuration via files, especially the
logs.jsonandtb_gateway.json- this bootstrap config defines the self provisioning credentials, an empty list of connectors and
remoteConfigurationset totrue
- this bootstrap config defines the self provisioning credentials, an empty list of connectors and
My goal is to provide a gateway that could be managed via Thingboard but bootstraps itself with some sane configurations.
After provisioning of the gateway, the bootstrap configuration should be reflected to Thingsboard. This bootstrap configuration can be changed by the user in Thingsboard afterwards.
What I am also interested in, if using remote configuration is the config ever written to disk or does it only life in the attributes of the gateway device in Thingsboard?
If such a bootstrapping is not possible by now, is there a chance to get it implemented? Or does it even make sense to have that functionality? If not, why not? ;)
Is there any other way to do such kind of bootstrapping?
Versions (please complete the following information):
- OS: SLES 15 with Docker Swarm
- Thingsboard IoT Gateway version: v3.8.0 via Docker image
- Python version: default from Docker image