NervesHubLink.Configurator behaviour (nerves_hub_link v2.7.2)
View SourceBehaviour for implementing a configurator.
Implementing a new one would typically be relevant if you need a new way of doing authentication or other configuration. New security hardware or a new way to make the private key, shared secret available.
If you want to control the firmware updates look at NervesHubLink.Client
instead.
Summary
Callbacks
@callback build(%NervesHubLink.Configurator.Config{ archive_public_keys: term(), connect: term(), connect_wait_for_network: term(), data_path: term(), device_api_host: term(), device_api_port: term(), device_api_sni: term(), fwup_devpath: term(), fwup_env: term(), fwup_public_keys: term(), fwup_task: term(), heartbeat_interval_msec: term(), host: term(), nerves_key: term(), params: term(), remote_iex: term(), request_archive_public_keys: term(), request_fwup_public_keys: term(), shared_secret: term(), sni: term(), socket: term(), ssl: term() }) :: NervesHubLink.Configurator.Config.t()
Functions
@spec build() :: NervesHubLink.Configurator.Config.t()
@spec fetch_configurator() :: atom()