@turnkey/http 1.1.1 → 1.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +11 -0
- package/README.md +3 -1
- package/dist/__generated__/services/coordinator/public/v1/public_api.client.d.ts +1 -1
- package/dist/__generated__/services/coordinator/public/v1/public_api.client.js +1 -1
- package/dist/__generated__/services/coordinator/public/v1/public_api.fetcher.d.ts +1099 -381
- package/dist/__generated__/services/coordinator/public/v1/public_api.fetcher.d.ts.map +1 -1
- package/dist/__generated__/services/coordinator/public/v1/public_api.fetcher.js +1 -1
- package/dist/__generated__/services/coordinator/public/v1/public_api.swagger.json +65 -5
- package/dist/__generated__/services/coordinator/public/v1/public_api.types.d.ts +26 -6
- package/dist/__generated__/services/coordinator/public/v1/public_api.types.d.ts.map +1 -1
- package/package.json +3 -3
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,16 @@
|
|
|
1
1
|
# @turnkey/http
|
|
2
2
|
|
|
3
|
+
## 1.2.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- The `createSubOrganization` request has been updated under the hood:
|
|
8
|
+
|
|
9
|
+
- Calling `.createSubOrganization` on our HTTP client will trigger an activity of type `CREATE_SUB_ORGANIZATION_V3` instead of `CREATE_SUB_ORGANIZATION_V2` previously.
|
|
10
|
+
- If there are any policies referencing `CREATE_SUB_ORGANIZATION_V2` specifically, they will no longer work out of the box if creating sub-orgs via SDK. These policies will need to be updated to allow `CREATE_SUB_ORGANIZATION_V3`. See policy examples related to access control [here](https://docs.turnkey.com/managing-policies/examples#access-control) for additional methods of constructing policies.
|
|
11
|
+
- `CREATE_SUB_ORGANIZATION_V3` supports everything `CREATE_SUB_ORGANIZATION_V2` supports, with the addition of a `privateKeys` field to atomically create a sub-org with private keys. If no private keys are desired, simply provide an empty array.
|
|
12
|
+
- **NOTE**: when reading `createSubOrganization` results, SDK users will now need to look at `activity.result.createSubOrganizationResultV3` instead of the previously valid `activity.result.createSubOrganizationResult`.
|
|
13
|
+
|
|
3
14
|
## 1.1.1
|
|
4
15
|
|
|
5
16
|
### Patch Changes
|
package/README.md
CHANGED
|
@@ -69,7 +69,9 @@ try {
|
|
|
69
69
|
});
|
|
70
70
|
|
|
71
71
|
// Success!
|
|
72
|
-
console.log(
|
|
72
|
+
console.log(
|
|
73
|
+
activity.result.createPrivateKeysResultV2?.privateKeys?.[0]?.privateKeyId
|
|
74
|
+
);
|
|
73
75
|
} catch (error) {
|
|
74
76
|
if (error instanceof TurnkeyActivityError) {
|
|
75
77
|
// In case the activity is rejected, failed, or requires consensus,
|
|
@@ -195,7 +195,7 @@ export declare class TurnkeyClient {
|
|
|
195
195
|
*/
|
|
196
196
|
stampGetUsers: (input: TGetUsersBody) => Promise<TSignedRequest>;
|
|
197
197
|
/**
|
|
198
|
-
* Get basic information about your current API user and
|
|
198
|
+
* Get basic information about your current API or WebAuthN user and their organization. Affords Sub-Organization look ups via Parent Organization for WebAuthN users.
|
|
199
199
|
*
|
|
200
200
|
* Sign the provided `TGetWhoamiBody` with the client's `stamp` function, and submit the request (POST /public/v1/query/whoami).
|
|
201
201
|
*
|
|
@@ -281,7 +281,7 @@ class TurnkeyClient {
|
|
|
281
281
|
};
|
|
282
282
|
};
|
|
283
283
|
/**
|
|
284
|
-
* Get basic information about your current API user and
|
|
284
|
+
* Get basic information about your current API or WebAuthN user and their organization. Affords Sub-Organization look ups via Parent Organization for WebAuthN users.
|
|
285
285
|
*
|
|
286
286
|
* Sign the provided `TGetWhoamiBody` with the client's `stamp` function, and submit the request (POST /public/v1/query/whoami).
|
|
287
287
|
*
|