Skip to content

Document proxy resource release gate - #81

Open
IlyaasK wants to merge 59 commits into
hypeship/browser-pool-data-source-acceptancefrom
hypeship/proxy-resource-contract
Open

Document proxy resource release gate#81
IlyaasK wants to merge 59 commits into
hypeship/browser-pool-data-source-acceptancefrom
hypeship/proxy-resource-contract

Conversation

@IlyaasK

@IlyaasK IlyaasK commented Jul 11, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • document the missing tagged Proxies.Update SDK surface
  • record name-only in-place mutation and replacement semantics for other proxy config
  • define the preferred write-only custom-password plus replacement-version design
  • document metadata-only import and runtime health exclusions
  • keep kernel_proxy resource conditional until both gates are accepted

API and state contract

The API supports rename by ID, but v0.76.0 is still the latest SDK and lacks client.Proxies.Update. Pending SDK PR #133 adds it for v0.77.0. Reads expose has_password, never plaintext; Terraform must not put custom passwords in ordinary state or claim import can recover them.

Scope

Docs only. No provider behavior, secrets, or generated SDK code changes. Import and CRUD remain deferred.

Tests

Full short tests, vet, gofmt, module checks, Terraform example formatting, Markdown links, and diff checks passed.


Note

Low Risk
Documentation-only change to release criteria; no code or provider behavior.

Overview
Tightens the late/conditional v1 gate for the kernel_proxy resource in docs/architecture.md: it stays deferred until write-only credential/import semantics are accepted and a tagged SDK exposes in-place rename (not only credential/import acceptance as before).

No provider, SDK, or runtime behavior changes—architecture documentation only.

Reviewed by Cursor Bugbot for commit 069b7c3. Bugbot is set up for automated code reviews on this repo. Configure here.

IlyaasK and others added 6 commits July 10, 2026 09:35
Set the durable v1 target and release gates before resource implementation begins.

Co-authored-by: Cursor <cursoragent@cursor.com>
Use the latest tagged SDK while keeping provider behavior unchanged.
Expose org-scoped project mutations without automatic retries so Terraform resource work can use the generated SDK safely.
Define the durable project schema and pure SDK conversion boundary before wiring resource lifecycle behavior.
Model definite, successful, and uncertain project creation without exposing a partial Terraform resource. Preserve recoverable identity on ambiguous outcomes and direct operators to import before retrying.
@IlyaasK
IlyaasK requested review from Sayan- and tnsardesai and removed request for Sayan- and tnsardesai July 11, 2026 12:28
IlyaasK added 8 commits July 13, 2026 09:29
Join all project flatten diagnostics in uncertain create outcomes so operators see every invalid durable field. Add a regression test covering simultaneous missing ID and name values.
Read projects by canonical state ID, remove state only for coded not-found responses, and reject malformed or identity-changing API responses. Cover the pure unregistered lifecycle core with focused tests.
Build SDK error and response fixtures before parallel Create subtests so helper failures use the owning parent test before child execution begins.
Build a name-only SDK patch for changed project plans, skip unchanged names, and reject unknown values before the network boundary.
Apply name-only patches by canonical state ID, skip no-op updates, and validate complete SDK responses before returning new Terraform state.
Implement non-force project deletion with explicit state-preserving diagnostics, idempotent coded-not-found handling, and focused status-boundary tests. Document the API's indistinguishable projects-disabled not-found response as a residual provider risk.
Seed imported project state with the exact non-empty canonical ID and an unknown name so the normal Read lifecycle settles durable state.
Translate Terraform create plans into the reviewed project creation core and persist recoverable identity before uncertain diagnostics. Keep registration deferred until the complete lifecycle is wired.
@IlyaasK
IlyaasK force-pushed the hypeship/browser-pool-data-source-acceptance branch from f3fde8a to e903631 Compare July 13, 2026 13:35
@IlyaasK
IlyaasK force-pushed the hypeship/proxy-resource-contract branch from e565887 to 481791a Compare July 13, 2026 13:35
@IlyaasK
IlyaasK force-pushed the hypeship/browser-pool-data-source-acceptance branch from e903631 to f837de4 Compare July 13, 2026 14:32
@IlyaasK
IlyaasK force-pushed the hypeship/proxy-resource-contract branch from 481791a to 7e3baa3 Compare July 13, 2026 14:32
IlyaasK added 4 commits July 13, 2026 11:24
Separate recovery guidance for creates with and without recoverable state, and normalize empty SDK errors so Terraform always reports an actionable reason.
Refresh validated durable state, remove only confirmed missing projects, and preserve pre-populated Terraform state on diagnostics or malformed input.
Translate Framework update requests into the tested project update core while preserving prior state on diagnostics and no-op plans.
Decode prior project state, delegate to the non-force delete core, and preserve Terraform ownership by returning diagnostics on malformed state or API failure.
@IlyaasK
IlyaasK force-pushed the hypeship/browser-pool-data-source-acceptance branch from f837de4 to d6ec19c Compare July 13, 2026 15:39
@IlyaasK
IlyaasK force-pushed the hypeship/proxy-resource-contract branch from 7e3baa3 to 3d98466 Compare July 13, 2026 15:39
IlyaasK added 2 commits July 20, 2026 14:50
Assert that the Framework delete adapter preserves the underlying core error detail, so the test verifies propagation rather than only the presence of an error.
Write exact imported identity with an unknown name and leave API validation to the normal Read lifecycle without requiring a configured client.
IlyaasK added 26 commits July 21, 2026 16:13
Assemble the reviewed extension lifecycle helpers behind a Terraform Plugin Framework resource, require local archive inputs only for create or replacement, and publish generated schema documentation. This makes the durable extension surface usable while keeping runtime operations out of Terraform.
Add an opt-in Terraform acceptance test that uploads a valid extension archive, verifies stable plans and import, replaces content by checksum, confirms the old object is deleted, and checks final cleanup. Extend the manual acceptance matrix and release guidance so the durable extension resource has an explicit real-API release gate.
Add a Terraform 1.11-compatible extension example that tracks exact archive bytes with filesha256, publish the same snippet and import forms in generated Registry docs, and update the example index. This gives users a validated durable upload workflow without bundling a binary archive.
Prefer the API's authoritative resolved profile ID and ordered extension IDs over echoed selectors, validate their raw response shape before writing Terraform state, and retain only an ID-based compatibility path for older responses. This prevents name selectors from becoming non-canonical durable state.
When Kernel resolves a pool's extension IDs to an empty list, retain Terraform's prior distinction between an omitted attribute and an explicitly empty list. Validate the authoritative response first so malformed data still fails visibly, and cover both convergence paths.
Expose exact browser pool lookup by ID or name with predictable project scoping. Keep the first slice limited to canonical identity, name, and durable size so runtime state cannot enter Terraform.
Read canonical profile and ordered extension IDs from the SDK response, with strict validation and ID-only fallback for legacy echoes. Keep runtime fields outside Terraform state.
Read proxy and launch-mode fields into durable data-source state. Reject explicit null or malformed SDK values and preserve known false booleans through Terraform serialization.
Read start URL, timeout, and fill rate into durable data-source state. Validate SDK response types and ranges while preserving omitted values and known zero.
Read viewport configuration into a typed Terraform object. Reject malformed dimensions and preserve omitted viewport and refresh-rate values without partial state.
Normalize SDK Chrome-policy JSON into stable Terraform string state. Keep loose maps at the response boundary and preserve absent or null policy compatibility.
Add opt-in acceptance coverage for ID and exact-name lookup, durable state flattening, no-drift planning, project overrides, and cleanup. Run it only from the manual acceptance matrix.
Record the missing tagged proxy rename surface and the write-only password/import design required before Terraform can safely manage proxies.
@IlyaasK
IlyaasK force-pushed the hypeship/browser-pool-data-source-acceptance branch from 7dc356a to f868d78 Compare July 21, 2026 20:15
@IlyaasK
IlyaasK force-pushed the hypeship/proxy-resource-contract branch from 509a776 to 069b7c3 Compare July 21, 2026 20:15
@IlyaasK
IlyaasK force-pushed the hypeship/browser-pool-data-source-acceptance branch 2 times, most recently from 5ada561 to 3259a54 Compare July 31, 2026 19:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant