The latest PlanetScale features and product launches.
We have shipped a new webhook event: deploy_request.pending_cutover.
This event will trigger when a deploy request is ready to apply the schema and is waiting on the user to confirm.
For deploy requests that have "auto_cutover" or "Auto apply" enabled, this webhook will not be sent.
This new event is now available in your webhook settings.
We just shipped an improvement to deploy requests. Now, you can optionally set your deploy requests to delete the development branch once fully complete.
You can do this by toggling a checkbox while the deploy request is running. This new setting is also available via the CLI and API.
It is disabled by default and must be enabled for each deploy request. The branch will only be deleted if the deployment is successful and the revert period is complete.
As of pscale version 0.205.0, you can create a deploy request with pscale deploy-request create db branch --auto-delete-branch and the setting will be enabled.
The create deploy request endpoint now has auto_delete_branch available. Set this parameter to true to enable the setting.
Two years ago we made an upgrade to our edge infrastructure that enabled better performance and reliability for your database connections.
A small number of databases are still using connection strings from before this change. In the coming weeks we are working on deprecating the usage of these strings and getting everyone upgraded.
We are sending emails to all account admins for databases which are still connecting via legacy strings.
You may also check the hostname for your connections tring. If it shows the ID for the database branch, then it is a legacy string.
Examples:
abcdeabc1234.us-east-1.psdb.cloudaws.connect.psdb.cloudTo update your connection string, go to the PlanetScale dashboard -> your database -> settings -> passwords.
Create a new password and update the hostname, username and password in your application.
We will be performing multiple brownout periods starting September 3rd, 2024. During these, connections to your database will stop working.
The purpose of the brownout periods is to help alert anyone who is still unintentionally using a legacy connection string.
After several brownout periods, we will re-evaluate usage again and send final notices to anyone still using a legacy connection string before fully deprecating.
If you are using an old version of the pscale CLI, you may see the following message when trying to use pscale shell or pscale connect.
Your version of pscale is too old and is using a deprecated connection method. Please update your CLI version.
If this impacts you, please update pscale to the latest version.
We want this process to be simple and painless for everyone. If this causes any difficulties for you, please reach out to our support team.
We've shipped a small update to the "Require administrator approval for deploy requests" setting. Now, if your database only has a single administrator, they can self-approve their own deploy requests.
If there is more than one administator, then self-approval is not allowed.
We have made an update to schema recommendations. Now when closing a recommendation, you can leave an optional comment explaining why the recommendation is being closed.
Comments support markdown.
We have updated all webhook payloads to include the database and organization names.
{
"timestamp": 1698252879,
"event": "branch.ready",
+ "organization": "my-org",
+ "database": "example_database",
"resource": { ... }
}
We have released a new API endpoint for retrieving your organization's audit logs.
/v1/organizations/:name/audit-logA new service token scope read_audit_logs has also been added. You may add this to your service token by visiting your service token settings.
We are removing support for versions of the PlanetScale CLI older than v0.182.0 (February 2, 2024). On July 1st, they will no longer be able to use the following commands:
pscale connectpscale shellpscale database dumppscale database restore-dumpPlease update your CLI to version v0.182.0 or later to continue using these commands.
Branch cluster size has been added to the PlanetScale API. Now you can programmatically change your cluster size via a service token. To use the endpoints, you will need the write_database permission.
We’ve just shipped a change to the layout of the PlanetScale app. The top-level navigation links are now along the left-hand side.
Why make this change? We needed to make room for new features. We were starting to be limited by the space available along the top navigation bar. The new side navigation allows for more space and keeps everything easily discoverable.
We are now publishing the rate of errors encountered by each database branch's VTGate to Datadog. You can graph these metrics by using the planetscale.vtgate.errors metric name within your Datadog widget and notebooks.
We've shipped an improvement to make navigating to your most frequently used databases easier. Starting today, you can pin the databases you use most frequently. To do this, open the database switcher at the top of the page, you'll see a new pin icon next to each database.
The organization switcher has been improved as well. It will show all of your pinned databases across all of your organizations.
Invoices have been added to the PlanetScale API. Now you can programmatically access your organizations billing data via OAuth or a service token. To use the endpoints, you will need the read_invoices permission.
Previously only available to Single-tenant and Managed customers, PlanetScale now provides private connection endpoints to GCP regions via GCP Private Service Connect for customers on Scaler Pro.
Previously only available to Single-tenant and Managed customers, PlanetScale now provides private connection endpoints to AWS regions via AWS PrivateLink for customers on Scaler Pro.
This is helpful in cases where your compliance mandates that your connections do not route through the public Internet, or for customers looking to save costs on their NAT Gateways.
Insights now supports filtering query patterns by 50th and 99th percentile query execution time. To find all query patterns that have a 50th percentile execution time above 250 milliseconds, for example, enter p50:>250 in the insights search box.
We now detect usage of legacy character sets and collations in your database and provide upgrade recommendations. Modern character sets and collations are faster, support a wider range of characters including emoji, and have improved sorting for multi-byte characters.
Today, we're introducing the ability to create global replica credentials for your PlanetScale database.
With replica credentials, it makes it easier to query your database's replicas and read-only regions by creating a password dedicated for replica use. These new credentials will be routed to the nearest read-only region with the lowest latency as new regions are added or removed without any code changes or even needing to reconnect.
Webhooks have graduated from beta and are now generally available. Since the beginning of beta we've added an additional event which will trigger whenever a new Insights anomaly event is detected.
Our Hobby plan has now been retired. All remaining databases on the Hobby plan have been slept. To access your data, you must either upgrade to Scaler Pro or wake your database from your dashboard. Waking your database will give you 24 hours to dump your data. Please view our Hobby plan deprecation documentation for more information.
You can now enable webhooks for database anomalies. With this new hook you can notify your team when PlanetScale has detected slower than expected queries on your database.
The webhook event is branch.anomaly and includes the full database branch information in the payload.
Deploy requests will now remember your auto-apply setting. If you turn it off, all future deploy requests will default to the setting being off.
We’ve released an improvement to the billing page. You can now set spend alerts for your PlanetScale Organization.
To enable monthly spend alerts, go to your organization billing page, click "Enable spend alerts", and enter the maximum spend amount. Organization admins will receive an email once monthly spend hits 75% and 100%.
Our Hobby plan will be retired on April 8th, 2024. As of March 6th, 2024, you are no longer able to create new Hobby databases. Please view our Hobby plan deprecation documentation for more information.
We are now publishing the CPU and memory usage of each database branch's primary node to Datadog. You can graph these metrics by using the planetscale.primary.cpu_usage and planetscale.primary.memory_usage metric names within your Datadog widgets and notebooks.
Today, we’re releasing schema recommendations inside of PlanetScale Insights.
With schema recommendations, you will automatically receive recommendations to improve database performance, reduce memory and storage, and improve your schema based on production database traffic.
Schema recommendations uses query-level telemetry to generate tailored recommendations in the form of DDL statements that can be applied directly to a database branch and then deployed to production.
To enable foreign key constraints in any unsharded PlanetScale database, go to your database’s ”Settings” page and check the box to Allow foreign key constraints.
On the database’s ”Dashboard” page, you will see a loading spinner that says it is “Enabling foreign key constraints.” Once it no longer shows, you can use foreign key constraints in your PlanetScale database!
For most cases, foreign key constraints should work as expected in PlanetScale. There are a few cases to be aware of that are unsupported or result in less ideal behavior. You can read more in the limitations section of the foreign key constraints documentation.
If you don’t have an existing PlanetScale database and have an existing internet-accessible MySQL or MariaDB databases that use foreign key constraints, you can also import it into PlanetScale using our database import tool.
You can now enable safe migrations on development branches. With safe migrations enabled on a branch, you’ll gain zero-downtime schema migrations, schema reverts, and protection against accidental schema changes. Also, now you can use a development branch with safe migrations enabled to set up a workflow with a “staging” branch. Previously, only production branches could have safe migrations enabled.
OAuth applications are now available to all PlanetScale users in a public beta. An OAuth application in PlanetScale allows you to get authorization from your users for which organizations and databases the PlanetScale API can interact with.
If you are interested in building on top of PlanetScale and allowing your users to authenticate with PlanetScale to gain management access to their organizations and databases, you can create your OAuth application in your PlanetScale organization’s Settings > OAuth applications page.
We are committed to remaining the best database for serverless and real-world applications that require massive scale. To support this effort, we are deprecating the Scaler plan. Beginning February 12th 2024, you will no longer be able to create a new Scaler database clusters.
Read the announcement blog post for more information.