This security scheme looks like this in OpenAPI ```yaml components: securitySchemes: oauth2: type: oauth2 flows: password: tokenUrl: http://localhost:35456/oauth2/token scopes: products:read: Permission to read/list products products:create: Permission to create products products:delete: Permission to delete products admin: Full permission including managing product inventories ``` We have implemented support for this flow in TypeScript through a generated hook and the idea would be to do something similar in other languages. ## Requirements * Continue to allow passing an access token. This could sidestep the hook logic and behave like regular HTTP Bearer auth. * Additionally, allow passing an object contain resource owner password credentials. The hook should use these to acquire tokens for various scopes (and reacquire if they expire). * Ensure environment variables work in both cases * It should be possible to pass an access token as an environment variable * It should be possible to pass the various credentials fields as environment variables * Prefer the token environment variable if present * Implement the disabled tests for this flow ## Notes * There is already an `oauth2Password` feature that can be added to Go's `features.ts`. * There is an `oauth2-password` test sdk that's part of our test suite and the basis for the TypeScript tests * `internal/oauth2/password.go` is where the security scheme is transformed into SDK fields. * `zSDKs/sdk-typescriptv2/src/lib/oauth2-sessions.ts` shows an example of oauth2 session store which is used to hold access tokens keyed by client and scopes.

**Description or Expected Behavior/Actual behavior:** Parameters are referenced correctly like so: ``` parameters: - $ref: "../../../parameters/library/section-key.yaml" ``` But the parameters are not being resolved and linted correctly when document validation occurs ``` ERROR validation error: [line 127] path-params - DELETE must define parameter sectionKey as expected by path /library/sections/{sectionKey} ERROR validation error: [line 127] path-params - GET must define parameter sectionKey as expected by path /library/sections/{sectionKey} ERROR validation error: [line 137] path-params - GET must define parameter sectionKey as expected by path /library/sections/{sectionKey}/{tag} ERROR validation error: [line 139] path-params - GET must define parameter sectionKey as expected by path /library/sections/{sectionKey}/refresh ERROR validation error: [line 141] path-params - GET must define parameter sectionKey as expected by path /library/sections/{sectionKey}/search ```

The following example was extracted from a customer spec and it was silently broken in some languages because the AST was flattening the union down to one member. We've added a new feature flag to the generator called `sliceUnions` to gradually support this feature across generator targets. The task is to implement support and test generation for PHP. Example: ``` responses: '200': description: A list of events content: application/json: schema: anyOf: - type: array items: $ref: '#/components/schemas/ClickEvents' title: ClickEvents - type: array items: $ref: '#/components/schemas/LeadEvents' title: LeadEvents - type: array items: $ref: '#/components/schemas/SaleEvents' title: SaleEvents ``` As part of fixing this issue: * Add `sliceUnions` to the feature list for php in `features.ts` * Remove the `unions-union-array` entry in php's `features.ts` file under `isTestSkipped`. * Add php to `x-speakeasy-test` list for the `unionOfArraysPost` operation in `uber.yaml` (provided test generation is implemented for php)

-

**Description or Expected Behavior/Actual behavior:** Allow the SDK to pass a reference to itself in the hook context, specifically to support our PDF request splitting functionality. Would like to create new `Request` objects and pass them to `sdk.general.partition_async` directly from within the hook. To do this effectively, the SDK should pass a reference to itself within the hook context. This would ensure that all configurations and logic within the SDK are consistently applied to these additional requests, streamlining the process and reducing the risk of errors. **Customer Description (if applicable):** Original Message: Hey all! I'd like to request that the sdk pass a reference to itself in the hook content. This is for our pdf request splitting which has a ­BeforeRequestHook like so: • Open the request. If the file param is a pdf, break it into N smaller files. Send each of these as a new httpx request. Return the last file for the SDK to process. Since we added these extra httpx calls underneath the SDK code, we have to copy over the retry config, and we'll miss out on any other changes to this logic. What I'd like to do is create a few new Request objects, and send the to sdk.general.partition_async from within the hook. The requester also referenced additional attachments: ­ split_pdf_hook.py ``` def before_request( ``` **Replication Steps (for bugs)/Use Case (for features):** They have implemented a `BeforeRequestHook` for handling PDF file uploads that operates as follows: * Upon receiving a request, if the `file` parameter is a PDF, it is split into `N` smaller files. * `N-1` of these files are sent as new `httpx` requests. * The last file is returned for the SDK to process as usual. Currently, because these additional `httpx` requests are being made outside of the SDK's original context, we are required to manually copy over the retry configuration and any other relevant settings. This approach risks missing future changes to the SDK's request handling logic. **Risks/Other Notes:**

@constantine said: > code samples in readme just ignore that variable

A lot of providers will expose a `insecure = true` config for testing, [example from openstack](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs#insecure)

-