@segment/public-api-sdk-typescript 34.2.0-b6130 → 34.3.0-b6159

package/model/warehouse1.ts

@@ -2,7 +2,7 @@
  * Segment Public API
  * The Segment Public API helps you manage your Segment Workspaces and its resources. You can use the API to perform CRUD (create, read, update, delete) operations at no extra charge. This includes working with resources such as Sources, Destinations, Warehouses, Tracking Plans, and the Segment Destinations and Sources Catalogs.  All CRUD endpoints in the API follow REST conventions and use standard HTTP methods. Different URL endpoints represent different resources in a Workspace.  See the next sections for more information on how to use the Segment Public API.
  *
- * The version of the OpenAPI document: 34.2.0
+ * The version of the OpenAPI document: 34.3.0
  * Contact: friends@segment.com
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -11,7 +11,7 @@
  */
 
 import { RequestFile } from './models';
-import { Metadata2 } from './metadata2';
+import { Metadata1 } from './metadata1';
 import { WarehouseV1 } from './warehouseV1';
 
 /**
@@ -22,7 +22,7 @@ export class Warehouse1 {
      * The id of the Warehouse.
      */
     'id': string;
-    'metadata': Metadata2;
+    'metadata': Metadata1;
     /**
      * The id of the Workspace that owns this Warehouse.
      */
@@ -51,7 +51,7 @@ export class Warehouse1 {
         {
             name: 'metadata',
             baseName: 'metadata',
-            type: 'Metadata2',
+            type: 'Metadata1',
         },
         {
             name: 'workspaceId',

package/model/warehouse2.ts

@@ -2,7 +2,7 @@
  * Segment Public API
  * The Segment Public API helps you manage your Segment Workspaces and its resources. You can use the API to perform CRUD (create, read, update, delete) operations at no extra charge. This includes working with resources such as Sources, Destinations, Warehouses, Tracking Plans, and the Segment Destinations and Sources Catalogs.  All CRUD endpoints in the API follow REST conventions and use standard HTTP methods. Different URL endpoints represent different resources in a Workspace.  See the next sections for more information on how to use the Segment Public API.
  *
- * The version of the OpenAPI document: 34.2.0
+ * The version of the OpenAPI document: 34.3.0
  * Contact: friends@segment.com
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -11,7 +11,7 @@
  */
 
 import { RequestFile } from './models';
-import { Metadata2 } from './metadata2';
+import { Metadata1 } from './metadata1';
 import { WarehouseV1 } from './warehouseV1';
 
 /**
@@ -22,7 +22,7 @@ export class Warehouse2 {
      * The id of the Warehouse.
      */
     'id': string;
-    'metadata': Metadata2;
+    'metadata': Metadata1;
     /**
      * The id of the Workspace that owns this Warehouse.
      */
@@ -51,7 +51,7 @@ export class Warehouse2 {
         {
             name: 'metadata',
             baseName: 'metadata',
-            type: 'Metadata2',
+            type: 'Metadata1',
         },
         {
             name: 'workspaceId',

package/model/warehouseAdvancedSyncV1.ts

@@ -2,7 +2,7 @@
  * Segment Public API
  * The Segment Public API helps you manage your Segment Workspaces and its resources. You can use the API to perform CRUD (create, read, update, delete) operations at no extra charge. This includes working with resources such as Sources, Destinations, Warehouses, Tracking Plans, and the Segment Destinations and Sources Catalogs.  All CRUD endpoints in the API follow REST conventions and use standard HTTP methods. Different URL endpoints represent different resources in a Workspace.  See the next sections for more information on how to use the Segment Public API.
  *
- * The version of the OpenAPI document: 34.2.0
+ * The version of the OpenAPI document: 34.3.0
  * Contact: friends@segment.com
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/model/warehouseMetadata.ts

@@ -2,7 +2,7 @@
  * Segment Public API
  * The Segment Public API helps you manage your Segment Workspaces and its resources. You can use the API to perform CRUD (create, read, update, delete) operations at no extra charge. This includes working with resources such as Sources, Destinations, Warehouses, Tracking Plans, and the Segment Destinations and Sources Catalogs.  All CRUD endpoints in the API follow REST conventions and use standard HTTP methods. Different URL endpoints represent different resources in a Workspace.  See the next sections for more information on how to use the Segment Public API.
  *
- * The version of the OpenAPI document: 34.2.0
+ * The version of the OpenAPI document: 34.3.0
  * Contact: friends@segment.com
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/model/warehouseMetadataV1.ts

@@ -2,7 +2,7 @@
  * Segment Public API
  * The Segment Public API helps you manage your Segment Workspaces and its resources. You can use the API to perform CRUD (create, read, update, delete) operations at no extra charge. This includes working with resources such as Sources, Destinations, Warehouses, Tracking Plans, and the Segment Destinations and Sources Catalogs.  All CRUD endpoints in the API follow REST conventions and use standard HTTP methods. Different URL endpoints represent different resources in a Workspace.  See the next sections for more information on how to use the Segment Public API.
  *
- * The version of the OpenAPI document: 34.2.0
+ * The version of the OpenAPI document: 34.3.0
  * Contact: friends@segment.com
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/model/warehouseSelectiveSyncItemV1.ts

@@ -2,7 +2,7 @@
  * Segment Public API
  * The Segment Public API helps you manage your Segment Workspaces and its resources. You can use the API to perform CRUD (create, read, update, delete) operations at no extra charge. This includes working with resources such as Sources, Destinations, Warehouses, Tracking Plans, and the Segment Destinations and Sources Catalogs.  All CRUD endpoints in the API follow REST conventions and use standard HTTP methods. Different URL endpoints represent different resources in a Workspace.  See the next sections for more information on how to use the Segment Public API.
  *
- * The version of the OpenAPI document: 34.2.0
+ * The version of the OpenAPI document: 34.3.0
  * Contact: friends@segment.com
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/model/warehouseSyncOverrideV1.ts

@@ -2,7 +2,7 @@
  * Segment Public API
  * The Segment Public API helps you manage your Segment Workspaces and its resources. You can use the API to perform CRUD (create, read, update, delete) operations at no extra charge. This includes working with resources such as Sources, Destinations, Warehouses, Tracking Plans, and the Segment Destinations and Sources Catalogs.  All CRUD endpoints in the API follow REST conventions and use standard HTTP methods. Different URL endpoints represent different resources in a Workspace.  See the next sections for more information on how to use the Segment Public API.
  *
- * The version of the OpenAPI document: 34.2.0
+ * The version of the OpenAPI document: 34.3.0
  * Contact: friends@segment.com
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/model/warehouseV1.ts

@@ -2,7 +2,7 @@
  * Segment Public API
  * The Segment Public API helps you manage your Segment Workspaces and its resources. You can use the API to perform CRUD (create, read, update, delete) operations at no extra charge. This includes working with resources such as Sources, Destinations, Warehouses, Tracking Plans, and the Segment Destinations and Sources Catalogs.  All CRUD endpoints in the API follow REST conventions and use standard HTTP methods. Different URL endpoints represent different resources in a Workspace.  See the next sections for more information on how to use the Segment Public API.
  *
- * The version of the OpenAPI document: 34.2.0
+ * The version of the OpenAPI document: 34.3.0
  * Contact: friends@segment.com
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -11,7 +11,7 @@
  */
 
 import { RequestFile } from './models';
-import { Metadata2 } from './metadata2';
+import { Metadata1 } from './metadata1';
 
 /**
  * Defines a data Warehouse used as a Destination for Segment data.
@@ -21,7 +21,7 @@ export class WarehouseV1 {
      * The id of the Warehouse.
      */
     'id': string;
-    'metadata': Metadata2;
+    'metadata': Metadata1;
     /**
      * The id of the Workspace that owns this Warehouse.
      */
@@ -50,7 +50,7 @@ export class WarehouseV1 {
         {
             name: 'metadata',
             baseName: 'metadata',
-            type: 'Metadata2',
+            type: 'Metadata1',
         },
         {
             name: 'workspaceId',

package/model/workspace.ts

@@ -2,7 +2,7 @@
  * Segment Public API
  * The Segment Public API helps you manage your Segment Workspaces and its resources. You can use the API to perform CRUD (create, read, update, delete) operations at no extra charge. This includes working with resources such as Sources, Destinations, Warehouses, Tracking Plans, and the Segment Destinations and Sources Catalogs.  All CRUD endpoints in the API follow REST conventions and use standard HTTP methods. Different URL endpoints represent different resources in a Workspace.  See the next sections for more information on how to use the Segment Public API.
  *
- * The version of the OpenAPI document: 34.2.0
+ * The version of the OpenAPI document: 34.3.0
  * Contact: friends@segment.com
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/model/workspaceV1.ts

@@ -2,7 +2,7 @@
  * Segment Public API
  * The Segment Public API helps you manage your Segment Workspaces and its resources. You can use the API to perform CRUD (create, read, update, delete) operations at no extra charge. This includes working with resources such as Sources, Destinations, Warehouses, Tracking Plans, and the Segment Destinations and Sources Catalogs.  All CRUD endpoints in the API follow REST conventions and use standard HTTP methods. Different URL endpoints represent different resources in a Workspace.  See the next sections for more information on how to use the Segment Public API.
  *
- * The version of the OpenAPI document: 34.2.0
+ * The version of the OpenAPI document: 34.3.0
  * Contact: friends@segment.com
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/package.json

@@ -18,7 +18,7 @@
         "uuid": "^8.3.2",
         "request": "^2.88.2"
     },
-    "version": "34.2.0-b6130",
+    "version": "34.3.0-b6159",
     "devDependencies": {
         "@types/bluebird": "^3.5.33",
         "@types/jest": "^29",

package/tests/__snapshots__/smoke.test.ts.snap

@@ -183,7 +183,7 @@ exports[`Smoke tests sends correct request and parses response for create 2`] =
         "enabled": true,
         "id": "source-id",
         "labels": [],
-        "metadata": Metadata1 {
+        "metadata": Metadata2 {
           "categories": [
             "Website",
           ],
@@ -469,7 +469,7 @@ exports[`Smoke tests sends correct request and parses response for list 2`] = `
           "enabled": true,
           "id": "source-id",
           "labels": [],
-          "metadata": Metadata1 {
+          "metadata": Metadata2 {
             "categories": [
               "Website",
             ],
@@ -642,7 +642,7 @@ exports[`Smoke tests sends correct request and parses response for read 2`] = `
         "enabled": true,
         "id": "source-id",
         "labels": [],
-        "metadata": Metadata1 {
+        "metadata": Metadata2 {
           "categories": [
             "Website",
           ],
@@ -813,7 +813,7 @@ exports[`Smoke tests sends correct request and parses response for update 2`] =
         "enabled": false,
         "id": "source-id",
         "labels": [],
-        "metadata": Metadata1 {
+        "metadata": Metadata2 {
           "categories": [
             "Website",
           ],