Releases: tsuru/tsuru-client
tsuru 1.2.0
-
app-run
command now supports a new flag-i/--isolated
. When this flag is set,
tsuru will spin up a new unit that will only live as long as the provided command is
running. Since this unit won't be routable, this is a nice way to run commands without affecting
your users. -
This releases adds all commands from
tsuru-admin
andcrane
on tsuru. Those clients are now marked as deprecated, all commands will leave in tsuru. -
certificate-set
sets a TLS certificate for an app -
certificate-unset
unsets a TLS certificate for a given app -
certificate-list
list TLS certificates for a given appInstaller (Experimental)
-
install-host-list
list hosts created and registered by the installer. -
install-ssh
enables login into or running a command on a host installed by the installer.
tsuru 1.1.1
tsuru 1.1.1 fixes the tsuru install
making it possible to create a local installation of tsuru.
tsuru 1.1.0
tsuru 1.1.0 matches the 1.1.0 release of tsuru server.
tsuru 1.0.1
tsuru 1.0.1 matches the 1.0.0 release of tsuru server.
1.0.1-rc1
deploy: send data in body instead of query string in app-deploy-rollb…
tsuru 0.18.1
tsuru 0.18.1 adds some improvements on top of 0.18.0, specifically on permission management.
Support was added for default roles, these roles can be automatically assigned to users after certain events. One possible use is to automatically grant permission to manage a team after creating it. The commands are:
tsuru role-default-add
: adds a new role to the list of default roles for an event;tsuru role-default-remove
: removes a new role from the list of default roles for an event;tsuru role-default-list
: list the default roles registered in tsuru.
tsuru 0.18.0
tsuru 0.18.0 matches the 0.13.0 release of tsuru server.
Features
- All service instance related commands now take the service as a parameter, as the name of instances are not globally unique anymore (they're unique per service) (tsuru/tsuru#1299)
- Restarting is now optional on
env-set
,env-unset
,service-bind
andservice-unbind
. The user might provide a--no-restart
flag to prevent restarting (tsuru/tsuru#1271) - New permission management commands (tsuru/tsuru#1278):
tsuru permission-list
lists currently available permissions (for creating new roles);tsuru role-list
lists currently available roles (that can be associated with users);tsuru role-add
creates a new role;tsuru role-remove
removes an existing role;tsuru role-permission-add
adds permissions to a role;tsuru role-permission-remove
removes permissions from a role;tsuru role-assign
associates a role with a user;tsuru role-disassociate
disassociates a role and a user.
tsuru user-list
is a new command that lists all users that have at least the same permissions as the user invoking the command (tsuru/tsuru#1278)
Bug fixes
tsuru env-set
now accepts variables with $ in the content (tsuru/tsuru#1301)- Fix table rendering with contents that contain new-line characters
General improvements
- New flag in the app-list command:
-q
. When provided, tsuru will display only application names (tsuru/tsuru#1269) - Change ordering in app-deploy-list
- Add an option for automatically unbinding service instances from apps when removing a service instance with
tsuru service-remove
(tsuru/tsuru#628) tsuru platform-list
now displays only enabled platforms (unless the user can view all platforms, in this case, disabled platforms are flagged in the list) (tsuru/tsuru#1284)- Privileged users can now use
tsuru token-show
andtsuru token-regenerate
to get tokens from third users (tsuru/tsuru#1316) tsuru app-info
now displays quota usage information (current and maximum allowed amount of units)tsuru app-info
now matches the name of the unit displayed bytsuru app-log
(tsuru/tsuru#1317)- tsuru now stores targets and tokens inside the
$HOME/.tsuru
directory, along with plugins. This avoids HOME polution (thanks Guilherme Garnier) (tsuru/tsuru#775 tsuru/tsuru#1290)
Deprecated commands
app-set-team-owner
has been renamed toapp-team-owner-set
Removed commands
- Because of the new authorization scheme, the following commands were removed, please use the new role and permission management commands instead:
tsuru team-user-list
tsuru team-user-add
tsuru team-user-remove
tsuru 0.17.1
tsuru 0.17.1 includes some bug fixes in the reporting of units, along with other changes:
- properly handle symbolic links to directories in
tsuru app-deploy
(tsuru/tsuru#1256) - do not display the "Did you mean?" message when there are no suggestions
tsuru 0.17.0
tsuru 0.17.0 matches the 0.12.0 release of tsuru server.
Features
- It's now possible to filter the output of
tsuru app-list
. You can check the available filters usingtsuru app-list --help
. Related to tsuru/tsuru#1134 and tsuru/tsuru#1210. tsuru app-shell
now uses WebSocket for communication, improving API compatibility with reverse proxies that support HTTP connection upgrades. tsuru/tsuru#1162tsuru app-info
now includes information about locks, reporting whether the application is locked or not, and for how long the application has been locked and who's the owner of the lock.- New command:
tsuru app-plan-change
. Yeah, it does what you think: it changes the plan of an application, taking two possible actions:- if the router changes, move application units and change its address
- if at least one of memory, swap or CPU changes, restart the application
- When running
tsuru team-list
, admin users now see all teams registered in remote server - New commands for managing access to service instances (
tsuru service-instance-grant
andtsuru service-instance-revoke
) - Process based management. The following commands are affected by lean containers (tsuru/tsuru#1136):
- app-stop, app-start and app-restart: there's an optional -p/--process parameter, allowing users to stop, start or restart only units running the specified process
- unit-add and unit-remove: there's a -p/--process parameter which is mandatory if the application has more than one process. Therefore, users can scale their units based on the process that they're running
- The output of
tsuru pool-list
now include the public pools (pools available to any user) tsuru/tsuru#1202
Bug fixes
tsuru app-deploy
now checks whether the user has access to the application before starting the upload (thanks Jonathan Prates) tsuru/tsuru#1190tsuru user-remove
no longer removes the .tsuru-token file. The motivation behind this feature relied on the fact that in the past, users were able to remove only themselves from tsuru, so logging out used to make sense, but now admin users can remove any user (thanks Dan Carley) tsuru/tsuru#1235tsuru key-add
now properly report failures when trying to override a key. Whenever a user tries to add a key that already exists, the command asks whether the user wants to override it. There's also a flag to force overriding without asking. tsuru/tsuru#1249
General improvements
- Improve the output of
tsuru app-deploy-list
when the application has no deploys
Deprecated commands
tsuru app-change-pool
has been renamed totsuru app-pool-change
tsuru 0.16.0
tsuru 0.16.0 matches the 0.11.0 release of tsuru server.
Features
tsuru app-remove
now always requires a-a <appname>
parameter to avoid accidents removing applications (thanks Lucas Weiblen). tsuru/tsuru#1106- New commands
tsuru pool-list
andtsuru app-change-pool
. It's now possible to have multiple pools available for deploying applications. - Added
tsuru user-info
command to return information about current logged user. - Improved error handling in
tsuru app-shell
(thanks Wilson Júnior). - Improved command suggestion for user errors (thanks Pablo Aguiar).
- Add manpage (thanks Gustavo Pantuza). tsuru/tsuru#596
- Users are now able to define private environment variables with
tsuru env-set
(thanks Diogo Munaro).
Bug fixes
tsuru app-shell
command now works with tsuru api under TLS. tsuru/tsuru#1148tsuru app-deploy
now works properly on Windows. tsuru/tsuru#1168- Token and target management functions now work properly on Windows. tsuru/tsuru#1169