Search Results for "secrets"

...The extension communicates securely with companion mobile or desktop clients to fetch or synchronize token data, respecting encryption and privacy boundaries so that secrets are never exposed to the extension itself without user consent. It also lets users manage or view registered accounts, add new ones by scanning QR codes via companion apps, and handle token organization from within browser UI elements.

...Because Home Assistant involves complex interdependencies between devices and automations, having a central config repo ensures changes are traceable and easily reverted. The repository often includes templates, secrets configuration, and skip-files to avoid committing sensitive credentials. For users running multiple installations or migrating devices, hass-config serves as the canonical definition of the automation state. It’s especially helpful for community users who share automations, troubleshoot setups, or onboard new devices.

...To create a custom logger define an options object yielding a types field with the logger data and pass it as argument to a new signale instance. By utilizing the secrets option, secrets and other sensitive information can be filtered out from the body as well as the metadata, i.e. scope names etc, of to-be-logged messages. The option is part of the configuration object passed to a Signale instance on its initialization, and is of type Array<String|Number>. The array can hold multiple secrets, all of which are removed, if present, from the to-be-logged messages and are replaced with the default '[secure]' string.