Plugins

This page describes all the plugins that are bundled with Taito CLI by default. You may find more plugins by browsing Taito CLI extensions.

Application control

Application control plugins typically implement the following commands:

• taito start: Start the application.
• taito stop: Stop the application.
• taito status: Show status of the application.
• taito restart: Restart container/function or the whole application.
• taito kill: Kill container/function or the whole application.
• taito scale: Scale container/function.
• taito logs: Tail logs of a container/function.
• taito shell: Start shell inside a running container.
• taito exec: Execute command inside a running container.
• taito forward: Forward local port to container port.
• taito copy from: Copy files from a running container.
• taito copy to: Copy files to a running container.

Plugins:

• docker-compose: Manage containers running on Docker Compose using Taito CLI commands.
• kubectl: Manage containers running on Kubernetes using Taito CLI commands.
• knative: Manage functions running on Knative using Taito CLI commands (TODO).

TIP: It is quite common to run Docker Compose in local development and Kubernetes on server environments. You can do this by enabling the docker-compose plugin for local environment and the kubectl plugin for all other environments.

NOTE: If your application is based on technologies that are not supported by existing Taito CLI plugins, you can implement the aforementioned application control Taito CLI commands in package.json, Makefile or Pipfile of your project. See the Build Tools section for npm, make and pipenv plugin descriptions.

Build tools

Build tool plugins typically implement the following:

• Pre-hook for running user defined scripts with Taito CLI (e.g. scripts in package.json, Makefile or Pipfile).
• taito env apply: Install libraries on host.
• Participate in the CI/CD process by implementing some of the taito commands.

Plugins:

• docker: Build and push Docker container images using the taito artifact prepare and taito artifact release commands.
• helm: Manage Helm deployments on Kubernetes using the taito deployment * commands.
• make: Execute make scripts with Taito CLI.
• npm: Execute npm scripts with Taito CLI.
• pipenv: Execute pipenv scripts with Taito CLI.
• semantic-release: Make a new release using the taito build release command. The semantic-release library will handle semantic versioning and release notes automatically based on your git commit messages.

You typically need to implement the following Taito CLI commands in package.json, Makefile or Pipfile of your project. Note that the commands should support also server environments in addition to the local development environment (expect for unit and check commands, that are run only locally or by CI/CD). See package.json of the full-stack-template as an example.

• taito init: Populate data sources with example data (databases, storages).
• taito info: Show info required for logging in to the application.
• taito unit: Run unit tests.
• taito test: Run integration and e2e tests. Taito CLI provides taito util-test command that may be useful for implementing these.
• taito code check: Check code quality.
• taito dep check: Check project dependencies (available upgrades, known vulnerabilities, etc.).
• taito size check: Check application size (webpack bundle size, for example).
• release-pre:prod and release-post:prod: Execute pre- and post-tasks for a production release (execute semantic-release, for example).

Cloud providers

Cloud provider plugins typically implement the following commands:

• taito auth: Authenticate to the cloud environment.
• taito db proxy: Start a proxy for accessing a remote database.
• Pre-hook that starts a db proxy automatically on demand and post-hook that stops the db proxy.

Plugins:

• aws: AWS cloud environment.
• azure: Azure cloud environment.
• gcp: Google Cloud environment.
• gcp-global: Google Cloud environment.
• ssh: For accessing virtual machines or dedicated servers with plain ssh.

CI/CD

CI/CD plugins typically implement the following commands:

• taito env apply: Create a build trigger (if build triggers are not managed with terraform)
• taito env destroy: Delete a build trigger (if build triggers are not managed with terraform)
• taito deployment start: Start a build manually.
• taito deployment cancel: Cancel an ongoing build.
• taito build prepare: Execute some additional preparations, if required.

Plugins:

• aws-ci: Use AWS Build as your CI/CD pipeline.
• azure-ci: Use Microsoft DevOps as your CI/CD pipeline.
• bitbucket-ci: Use BitBucket Pipelines as your CI/CD pipeline.
• gcp-ci: Use Google Cloud Build as your CI/CD pipeline.
• github-ci: Use GitHub actions as your CI/CD pipeline.
• gitlab-ci: Use GitLab CI/CD as your CI/CD pipeline.
• jenkins-ci: Use Jenkins as your CI/CD pipeline (TODO).
• tekton-ci: Use Tekton as your CI/CD pipeline (TODO).

Databases

Database plugins typically implement the following commands:

• taito db *: Manage database with Taito CLI commands.
• taito env apply: Create a database and database users (if not managed with terraform)
• taito env destroy: Delete a database and database users (if not managed with terraform)
• taito secret rotate: Set new database user passwords (if not managed with terraform)

Plugins:

• mysql-db: Taito CLI support for MySQL.
• postgres-db: Taito CLI support for PostgreSQL.
• sqitch-db: Taito CLI support for Sqitch.

Hour reporting

Hour reporting plugins typically implement the following commands:

• taito hours *: Hour reporting with Taito CLI commands.

Plugins:

• jira-tempo: Taito CLI support for JIRA Tempo (TODO).
• toggl: Taito CLI support for Toggl.

TIP: You can report your work hours to multiple hour reporting systems at once with a single Taito CLI command. You just need to enable multiple hour reporting plugins. For example, if one of the plugins should always be enabled and the other one only when you are working with a certain project, you can enable one plugin globally in you default taito-config.sh file, and the other one in the taito-config.sh file of the project. On the other hand, if both plugins should be enabled when you are working for a certain organization, you can enable both plugins in the taito-config.sh file of the organization.

Infrastructure management for projects

Project infrastructure management plugins typically implement the following commands:

• taito env apply: Apply infrastructure changes for a project environment.
• taito env destroy: Remove project environment.

Plugins:

• ansible
• terraform

Infrastructure management for zones

Zone infrastructure management plugins typically implement the following commands:

• taito zone *: Manage zone with Taito CLI commands.

Tool plugins:

• ansible-zone
• helm-zone
• kubectl-zone
• terraform-zone

Cloud provider plugins:

• aws-zone
• azure-zone
• gcp-zone
• do-zone

Issue management

Issue management plugins typically implement the following commands:

• taito issue *: Issue management with Taito CLI commands.

Plugins:

• github-issues: Taito CLI support for GitHub issues (TODO).
• gitlab-issues: Taito CLI support for GitLab issues (TODO).
• jira-issues: Taito CLI support for JIRA issues (TODO).

Miscellaneous

• basic: The basic plugin is always enabled. It implements some of the basic Taito CLI functionality like taito --help, taito readme and taito trouble.
• docker-global: Clean up your Docker with the taito workspace clean and taito workspace kill commands.
• links-global: Provides support for links by implementing the taito open * and taito link * commands. Also generates links to project README.md on taito project apply and taito project generate.
• run: TODO: description.
• template-global: Provides support for project templates by implementing the taito project create, taito project upgrade and taito project migrate commands.

Monitoring and error tracking

Plugins:

• aws-monitoring: TODO
• azure-monitoring: TODO
• gcp-monitoring: Lists available monitoring channels, etc.
• sentry: Creates a Sentry project on taito project apply.

You can open monitoring systems on your browser with the following commands, if the links have been configured in taito-config.sh file of your project.

• taito open uptime: Poll-based uptime monitoring.
• taito open performance: Performance monitoring.
• taito open logs: Logs.
• taito open errors: Error tracking.
• taito open feedback: User feedback.

Password management

Password management plugins are meant for managing commonly shared passwords. Typically they implement the following commands:

• taito passwd share: Share a password with anymore (e.g. with a one-time magic link).
• taito passwd list: List passwords.
• taito passwd get: Get password.
• taito passwd set: Set password.
• taito passwd rotate: Rotate passwords.

Plugins:

• gcp-passwd-global:

Secret management

Secret management plugins typically implement the following commands:

• taito secret show: Load and show the secrets.
• taito secret rotate: Create and store secrets on secret rotate.
• taito env apply: Create and store secrets on env apply.
• Pre-hook for reading a secret on demand.

Plugins:

• default-secrets: Uses stag environent secrets as default values for prod secrets, prod environent secrets as default values for stag secrets, and dev secrets as default values for all other environments.
• generate-secrets: Generates secret values on demand either by generating random values or by querying secret details from user.
• aws-secrets: Uses AWS Systems Manager to store or backup secrets.
• gcp-secrets: Uses Google Cloud KMS and Google Cloud Storage to store or backup secrets (TODO).
• kubectl: Uses Kubernetes to store secrets.
• vault-secrets: Uses Vault to manage secrets (TODO).

TIP: You can enable multiple secret plugins at the same time. For example, enable the kubectl plugin so that secrets are available for Kubernetes deployments. Additionally, enable the gcp-secrets plugin so that at least non-random secrets will be saved to a storage bucket just in case you accidentally delete secrets from Kubernetes.

Services

Service plugins typically implement the following commands:

• TODO: Taito CLI commands for managing services

Plugins:

• istio TODO

Storage

Storage plugins typically implement the following commands:

• taito storage *: Manage storage buckets.

Plugins:

• aws-storage: Taito CLI support for AWS storage buckets (S3).
• azure-storage: Taito CLI support for Azure storage buckets.
• gcp-storage: Taito CLI support for Google Cloud storage buckets.
• do-storage: Taito CLI support for DigitalOcean storage buckets (TODO).

Version control

Version control plugins typically implement the following commands:

• taito env: Version control commands for Taito CLI (manage environment, feature and hotfix branches).
• taito feat: Version control commands for Taito CLI (manage environment, feature and hotfix branches).
• taito commit: Version control commands for Taito CLI (manage environment, feature and hotfix branches).

Plugins:

• git