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
Commit b40a3c4
Browse filesBrowse the repository at this point in the historyBrowse files
fix(isolation): run cloud.gov CF CLI fetch after CA trust
The CF CLI download ran in `phase: install` (create time), before the
CA-trust kit's startup step trusted an intercepting proxy's CA. On sbx
behind Zscaler, curl exited 60 and the whole sandbox create failed.
- Run the fetch as a non-fatal, idempotent `phase: startup` command as
the agent user, installing into ~/.local/bin, so it follows the CA kit
in kit order. No root step executes the agent-writable script.
- Allow release-assets.githubusercontent.com: github.com redirects the
pinned release tarballs there.
- verify: add ACQ_BACKEND=sbx|msb (passes --backend to acq, fails if the
create log names a different backend), a fetch-ordering check, and CA_KIT
for bundles with no CA kit.
- Add an offline regression test that simulates an intercepted network
(curl exits 60 until the CA is trusted), plus SHA-256 mismatch and
non-fatal wrapper cases.
- Docs: do not add a CA kit the bundle already has (sbx rejects duplicate
kit names).
Co-authored-by: OpenCode Agent <[email protected]>
|`github.com`, `objects.githubusercontent.com`| Pinned Cloud Foundry CLI release tarball download during kit install; if runtime access to these hosts is not acceptable for a deployment context, use a base image with `cf` preinstalled or a project-specific vetted artifact source. |
133
+
|`github.com`, `objects.githubusercontent.com`, `release-assets.githubusercontent.com`| Pinned Cloud Foundry CLI release tarball download during the startup install; if runtime access to these hosts is not acceptable for a deployment context, use a base image with `cf` preinstalled or a project-specific vetted artifact source. |
110
134
111
135
The kit intentionally does not allow `*.cloud.gov`. If the project needs a
112
136
specific app route, route service, or custom domain, add that exact host in a
@@ -153,8 +177,17 @@ Run the bundled check:
153
177
154
178
By default it runs offline checks only: repository kit validation, shell syntax
155
179
for kit scripts, auth-script guard tests with synthetic placeholders, and exact
156
-
egress allow-list assertions. Set `RUN_ACQ=1` to create a throwaway sandbox and
180
+
egress allow-list assertions, and that the CF CLI fetch is not an install-phase
181
+
command. Set `RUN_ACQ=1` to create a throwaway sandbox and
157
182
verify that `cf` is installed, cloud.gov/docs endpoints are reachable, and the
158
183
injected placeholder reaches the CF API through a direct HTTPS request.
159
-
`RUN_ACQ=1` requires a global `cloud-gov` acq secret. Set `KEEP=1` with
184
+
`RUN_ACQ=1` requires a global `cloud-gov` acq secret. On an
185
+
intercepted network, run it as is: the global bundle supplies the CA kit ahead
186
+
of this one, which is the live regression for the CA-before-fetch ordering. Set
187
+
`CA_KIT=<path>` only if your bundle has no CA-trust kit (a kit with the same
188
+
name as one already in the bundle is rejected by sbx). Set
189
+
`ACQ_BACKEND=sbx` (or `msb`) to pass `--backend` to `acq` without changing your
190
+
persisted default; the CA-before-fetch failure only reproduces on sbx, because
191
+
msb trusts host CAs natively. The script prints which backend the create log
192
+
names and fails if it differs from the one requested. Set `KEEP=1` with
0 commit comments