plugins

The plugins commands show the WordPress plugins of one environment and update them through Kinsta. The themes commands work the same way. To look across all sites of the company, see kinstactl company plugins.

kinstactl plugins list my-site --env live
kinstactl plugins list my-site --env live --updates
kinstactl plugins update my-site --all --env live

plugins list

List the plugins of an environment.

kinstactl plugins list my-site --env live --updates

kinstactl plugins list [site] [options]

List the plugins of an environment

Arguments

Argument	Description
site	site name or ID

Options

Option	Description
--env <env>	environment name or ID
--updates	only plugins with an update available

Global options --profile, --json and --no-input apply too. See scripting and CI.

Kinsta API: GET /sites/environments/{env_id}/wp-plugins

The table shows each plugin with its status, version, the version it can be updated to and whether the installed version is known to be vulnerable. --updates keeps only the plugins with an update available.

plugins update

Update one plugin, or all plugins with an update.

kinstactl plugins update my-site akismet --env live

kinstactl plugins update <site> [name] [options]

Update one plugin, or all plugins with an update

Arguments

Argument	Description
site	site name or ID
name	plugin name

Options

Option	Description
--env <env>	environment name or ID
--all	update every plugin that has an update
--dry-run	print the resolved target and request; change nothing
--no-wait	return the operation ID instead of waiting
--timeout <minutes>	give up waiting after this many minutes (default 30)

Global options --profile, --json and --no-input apply too. See scripting and CI.

Kinsta API: GET /sites/environments/{env_id}/wp-plugins, PUT /sites/environments/{env_id}/plugins, PUT /sites/environments/{env_id}/plugins/bulk-update

Pass either a plugin name as shown by plugins list, or --all, not both and not neither; both mistakes are USAGE errors. A plugin that is not installed or already up to date also fails with a USAGE error, while --all with nothing to update just reports that all plugins are up to date. Updates are not destructive and need no confirmation, but they do change a running site. Check what would be sent first with --dry-run:

kinstactl plugins update my-site --all --env live --dry-run

Updating waits for Kinsta to finish by default, and accepts --no-wait and --timeout <minutes>; see operations.