You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Payload deploys can set host, urlPath, isolated and branchedDatabases #3043
A CI pipeline builds a component and uploads it, which makes it a payload deploy. The root-config fields that make an application host-routed, isolated or branched can only be set by a package deploy:
host and urlPath fail validation without package (components/operationsValidation.js:609-610).
branchedDatabases is accepted and then ignored (filed separately as a bug).
set_configuration can't write arbitrary application keys either; it allows only <name>_package and <name>_port. So there's no supported way to deploy a built bundle as an isolated, host-bound, branched application, which is what a PR preview is.
Proposal
Accept these fields on payload deploys, and publish them in the component's root-config entry as an effect of the activation transaction (#2315 step 3), the same way package deploys do. A payload redeploy that omits a field keeps the existing value, as isolated already does.
Done when
harper deploy project=shop-pr-12 host=fix-cart.shop.example.com isolated=true branchedDatabases=true from a directory produces an isolated, host-bound, branched application.
A rejected or rolled-back build leaves these fields unchanged, with the same guarantees step 3 gives package.
Activity
Test a PR preview deployed from a build, end to end
Let payload deploys set host, urlPath, isolated and branchedDatabases
Test a PR preview deployed from a build, end to end
Test a PR preview deployed from a build, end to end