Today we're releasing a significant improvement to our CLI with the ability for any user to log in via their Knock account.
Previously, in order to use the CLI, you would have to use a service token to authenticate. Service tokens are great for non-local, shared environments, like when using Knock inside your CICD pipeline. However, for engineers who want to work with their Knock resources locally, requiring them to create a service token was an unnecessary extra step.
Now, Knock users can simply knock login to gain access to the CLI and get started managing their Knock workflows, templates, and more in code. You'll be redirected from the CLI to your browser to authenticate and grant access to your Knock account. Users who have authenticated with the CLI will then be granted the same permissions they have in the dashboard.
We’re excited to make it even easier for you and the engineers in your organization to work with Knock locally via our CLI. You can read more and get started today via the docs.
Fixes and improvements
- 🐛 [Dashboard] We fixed an issue where resetting a variable could set the variable to an empty string, causing the default to not be applied.
- 🐛 [Dashboard] We fixed an issue with casing of custom fields during CSV upload mapping.
- 👀 [SDK] We've added the ability to opt out of inline-identify in the JS and React SDKs.
