Laravel Cloud

Sync an environment with a Laravel Cloud environment's variables.

Connection

What	This provider
Vendor	Laravel Cloud
Key	`laravel-cloud-env`
Availability	`available`. You can connect it today.
Credential we hold	`laravel-cloud-token`
Values read back	yes
Activation	`on-next-deploy`

Direction	What it does
`import`	We read names and values out of the store into your environment.
`export`	We write names and values from your environment into the store.

on-next-deploy. A new value waits there and arrives with your next deploy.

Direction	Policies you can pick
`import`	`skip_existing`, `new_version`, `fail`
`export`	`create_only`, `overwrite`, `overwrite_and_prune`

How syncs work says what each one does.

Paste a credential from the vendor. We seal it and never show it again.

Field	Label	Kind	Required	What it is
`token`	API token	secret; we mask it here and seal it	yes	Create it under Organization settings, API tokens. Tokens expire after 1 month, 6 months or 1 year, so mint a new one before yours runs out. If you scope it, allow viewing environment variables, plus managing them to export.

You answer these once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`environmentId`	Environment ID	text	yes	no	Run cloud environment:list in the Laravel Cloud CLI and copy the ID column. The name and slug are different values. We sync the environment's own variables. Organization secrets attached to it are never read or pruned, and export stops, before any write, on a key one of them sets.

We probe for these when we verify the connection.

Permission	Directions	Blocking	Without it
`Permission to view environment variables`	every direction	yes	Preview cannot read the environment's variables, so nothing can be compared.
`Permission to manage environment variables`	`export`	yes	Export cannot add, change or delete a variable.