www/src/content/docs/blog/update-permalinks.mdx
import { Image } from "astro:assets"
import updatesLight from '../../../assets/blog/sst-console-updates-light.png'; import updatesDark from '../../../assets/blog/sst-console-updates-dark.png';
Moving forward, every update made to an SST v3 app will get a unique URL; a permalink. This is printed out by the SST CLI.
↗ Permalink https://sst.dev/u/318d3879
These permalinks redirect to a page in the Console. Check out a short video of this in action.
<picture> <source srcset={updatesDark.src} media="(prefers-color-scheme: dark)" /> <source srcset={updatesLight.src} media="(prefers-color-scheme: light)" /> <Image src={updatesLight} alt="SST Console Updates" /> </picture>Here you can view:
You'll need to have your AWS account connected to the Console to view these details.
The permalinks are useful for.
sst.config.ts have been applied correctly.sst dev locally; now you can send this link to a teammate. And they can view the full event log instead of asking you to send them the log file from your local machine.In addition to the state updates, the SST CLI also uploads the event log from every update to the S3 state bucket in your AWS account. It also generates a globally unique id for the update.
If your AWS account is connected to the Console, it pulls this state and generates the details for the update permalink. This also means that the Console can only show you updates after your AWS account has been connected.
When you visit the permalink, the Console looks up the id of the update and redirects you to the right app in your workspace.
You can learn more about updates in the Console and how state works over on the docs.