When you deploy a PowerTools service, infrastructure is automatically provisioned and your packaged code is deployed to the environment of your choice.
PowerTools automatically provisions infrastructure and deploys your code in a robust and reliable manner.
As you evolve your
service.yml schema and deploy, your infrastructure will evolve over time. Each deployment will
automatically create the required dns entries, load balancers, configs, deployments and other resources for your service
Most deployments are zero down time and instant.
The first time you deploy a new service, it might take up to 10 minutes to provision an SSL certificate. This latency occurs because PowerTools relies on AWS and GCP built in certificates where possible.
Deployments that do not involve changing component types in your
service.yml schema (such as moving a component from
static-public), are almost instantaneous. For instance, deploying a static site change and
refreshing the CDN cache takes just a few seconds for most apps.
When you do change component types, some downtime may occur as PowerTools updates your infrastructure.
When adding or removing components, be sure to deploy to a test environment first.
Since each build is declarative and corresponds to a point in time commit, each deployment is also declarative.
This means that at any given time, you can rollback or deploy a previous commit and your infrastructure, code, secrets and configs will exactly represent the state at that commit.
PowerTools writes a deployment manifest to your cloud on each deployment as well.