You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 18, 2025. It is now read-only.
Today wt-cli supports multiple profiles allowing you to specify --profile with each command to use that profile for execution.
When doing a bunch of steps or even scripting them, it's annoying to have to pass --profile over and over.
Proposal
Introduce a wt profile current [name] command which will set and persist the selected profile name. if current is set, that profile will be used by default. By default current will be set to "default". If a user decides to change to a different profile they can use the new command.
The state would be persisted locally (like in the .webtask file) and not as part of their account.
If the current profile is deleted, then an error will be returned if a command is executed. This ensures that the user knows that the profile is gone, rather than automatically falling back to another profile.
The text was updated successfully, but these errors were encountered:
Overview
Today wt-cli supports multiple profiles allowing you to specify
--profile
with each command to use that profile for execution.When doing a bunch of steps or even scripting them, it's annoying to have to pass
--profile
over and over.Proposal
Introduce a
wt profile current [name]
command which will set and persist the selected profile name. if current is set, that profile will be used by default. By default current will be set to "default". If a user decides to change to a different profile they can use the new command.The text was updated successfully, but these errors were encountered: