✽ Sync staged changes#2730
Merged
Merged
Conversation
…n Prod Config (APIX-981) * fix(dns): Exclude dns_records From combineCloudflareResources in Prod Config (APIX-981)
* feat(access): add idp_federation_grants resource Add list/create/get/delete endpoints for Access IdP federation grants under zero_trust.access. Closes AUTH-8707
* feat(api): sync workflows API endpoints (2 new) * chore: drop TODO(linguini) stub comments * chore: drop instances/terminate stub (now skipped from sync) * chore: sync workflows API endpoints into stainless config
…shares
* fix(resource_sharing): update share_resource method paths to match share-api rename
share-api MR !426 renamed the path placeholder on the share-resource
endpoints from {resource_id} to {share_resource_id} (the OpenAPI metadata
name only; URLs unchanged). The Stainless config's method-to-path
mapping still referenced the old name, so after the new spec flowed
through, Stainless couldn't resolve GET/PUT/DELETE on
/accounts/{account_id}/shares/{share_id}/resources/{...} and emitted
empty Read/Update/Delete handlers in the Terraform target. The Go SDK
target dropped those methods entirely.
Update both the production config and the testdata copy so the method
strings match the renamed path. Stainless's next codegen run will
restore the full CRUD surface for cloudflare_share_resource and the
corresponding methods in cloudflare-go's resource_sharing.Resources.
Ref: GRM-887
Related: cloudflare/grm/share-api!426 (the OpenAPI rename)
Cherry-pick of staging !911.
* fix(resource_sharing): drop bulk-replace recipients endpoint to fix codegen
* fix(resource_sharing): drop bulk-replace recipients endpoint to fix codegen
The Stainless model generator conflates the single-object create endpoint
(POST /shares/{share_id}/recipients) with the bulk-replace endpoint
(PUT /shares/{share_id}/recipients) when both are mapped under the same
subresource. The resulting model has a list-typed `body` field whose
MarshalJSON serializes the list as a JSON array on both create and
update — producing 400 errors on every single-recipient create.
Removing the bulk-replace mapping makes Stainless generate a model with
a single-object body, which the API accepts for create. Users wanting
to replace all recipients at once can issue successive create/delete
operations or hit the API directly.
Ref: GRM-887
* feat(resource_sharing): add Terraform resource definitions for shares
* feat(resource_sharing): add Terraform resource definitions for shares
Add terraform: blocks to resource_sharing and its subresources
(recipients, resources) so Stainless generates Terraform resources:
- cloudflare_share (full CRUD)
- cloudflare_share_recipient (create, read, delete, bulk-replace)
- cloudflare_share_resource (full CRUD)
Also adds the PUT /shares/{share_id}/recipients bulk-replace endpoint
to the recipients subresource.
Ref: GRM-887
* feat(dex): add device ISPs endpoint mapping
* feat(dex): move isps to DEX > devices > isps list resource
* feat(dex): add device ISPs endpoint mapping
Map GET /accounts/{account_id}/dex/devices/{device_id}/isps to
zero_trust.dex.device_isps.list for SDK generation.
Ref: APIX-630
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was automatically created to sync staged changes from Stainless to the next branch. New commits will be added to this PR as they are staged.