Skip to main content
This page covers the changes you make to a first-party integration after you set it up. They live in the Manage area below the checklist on the integration page, in this order: Domains, Proxy credential, Cloudflare token, Probe zone, Edge adapter, Advanced, and Remove. Only owners and admins can make these changes, and the dashboard asks you to verify your identity before each one.

Rename an integration

Select the pencil icon next to the integration’s name. A name appears only in the dashboard, so renaming changes nothing on your CDN, and you can rename an integration while an operation is running.

Change the domains an integration serves

Domains turns Serve every domain routed to this integration on or off. It isn’t shown while an integration is draining, and you can’t change the setting while another operation is running. See Serve several domains for what each setting covers. What happens after a change depends on the deployment: When you turn the setting on, update the publishable key’s allowed origins first, so the new domains can start sessions.

Rotate the proxy credential

The proxy credential authenticates your edge to Foil. To rotate it on an installed integration, select Rotate under Proxy credential. What happens next depends on who runs the edge: Foil accepts both credentials until your edge sends the new one, so nothing breaks while you roll it out. You can’t start another rotation, or rotate a draining integration, while one is in progress. For when the old credential on an edge you run is retired, see Credential rotation.

Replace the Cloudflare token

To replace the token Foil uses to deploy to Cloudflare, select Replace Cloudflare API token under Cloudflare token. Foil stops using the old token once it saves the new one. Revoke the old token in Cloudflare afterward. A CloudFront integration that Foil deploys has no stored credential to replace. Foil assumes your deployment role with the integration’s external ID for each operation, so you control access through the role’s trust policy.

Update your own edge

Foil updates the edges it deploys on Cloudflare and CloudFront. When you run the edge yourself, Edge adapter shows the version your edge reports and whether a newer one is available.

Redeploy or roll back the SDK

Foil keeps each installed integration on the current SDK release, so you don’t need to update anything to receive new releases. To decide yourself when a release reaches your pages, pin a release through the integration instead. Redeploy and Roll back don’t change the release a pinned page loads. Advanced has two controls that you rarely need:
  • Redeploy redeploys the edge with the current release and adapter. On an edge you run, it changes nothing on your CDN.
  • Roll back restores the previous SDK release. Foil holds the integration on that release for 24 hours, then resumes automatic updates.

Remove an integration

Removal happens in two stages so that sessions in progress can finish.
  1. Move your pages off the integration. Point them back at cdn.usefoil.com or at another integration.
  2. Under Remove, select Start draining. New sessions through the integration fail, and sessions already in progress keep working for 24 hours. A draining integration can’t be reactivated. To use the same URL again, create a new integration after removal.
  3. After 24 hours, select Remove integration. Keep the DNS records in place until removal finishes.
  4. Delete the ownership TXT record.
What removal does depends on the deployment: Foil refuses to delete a Worker, function, or distribution origin whose configuration no longer identifies it as the integration’s, so it never removes resources it didn’t create.

Probe zones

Coming soon. A first-party probe zone will let the network edge probe run on a subdomain of your own domain, such as probe.example.com, instead of Foil’s zone, *.e2.usefoil.com. Until then, Probe zone says that probe zones aren’t available yet, and the probe runs on Foil’s zone for every session with no DNS changes. A verified probe zone will apply to every site and session in your organization, so you’ll need to add https://*.<probe zone> to connect-src on every site that runs Foil, alongside https://*.e2.usefoil.com.