pika-shared 1.4.9 → 1.4.10
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/dist/types/chatbot/chatbot-types.d.mts +16 -0
- package/dist/types/chatbot/chatbot-types.d.ts +16 -0
- package/dist/types/chatbot/chatbot-types.js.map +1 -1
- package/dist/types/chatbot/chatbot-types.mjs.map +1 -1
- package/dist/util/server-utils.js.map +1 -1
- package/dist/util/server-utils.mjs.map +1 -1
- package/package.json +1 -1
|
@@ -2768,6 +2768,22 @@ interface PikaConfig {
|
|
|
2768
2768
|
pikaServiceTags?: Record<string, string>;
|
|
2769
2769
|
/** Additional tags applied only to the Pika Chat stack (merged with common, overwrites on conflict) */
|
|
2770
2770
|
pikaChatTags?: Record<string, string>;
|
|
2771
|
+
/**
|
|
2772
|
+
* The platform will tag each component of infrastructure with a name. This is the tag names to use for the component tags.
|
|
2773
|
+
* If not populated, then you will not get any component tags. Here are examples of a component tag assuming this array
|
|
2774
|
+
* contains `['component']`:
|
|
2775
|
+
*
|
|
2776
|
+
* ```
|
|
2777
|
+
* // Useful so in cost explorer you can break down the costs by inference profile
|
|
2778
|
+
* component: ${profileName}InferenceProfile
|
|
2779
|
+
*
|
|
2780
|
+
* // Useful so in cost explorer you can break down the costs by component
|
|
2781
|
+
* component: ${componentName}
|
|
2782
|
+
* ```
|
|
2783
|
+
*
|
|
2784
|
+
* @since 0.14.0
|
|
2785
|
+
*/
|
|
2786
|
+
componentTagNames?: string[];
|
|
2771
2787
|
};
|
|
2772
2788
|
}
|
|
2773
2789
|
/**
|
|
@@ -2768,6 +2768,22 @@ interface PikaConfig {
|
|
|
2768
2768
|
pikaServiceTags?: Record<string, string>;
|
|
2769
2769
|
/** Additional tags applied only to the Pika Chat stack (merged with common, overwrites on conflict) */
|
|
2770
2770
|
pikaChatTags?: Record<string, string>;
|
|
2771
|
+
/**
|
|
2772
|
+
* The platform will tag each component of infrastructure with a name. This is the tag names to use for the component tags.
|
|
2773
|
+
* If not populated, then you will not get any component tags. Here are examples of a component tag assuming this array
|
|
2774
|
+
* contains `['component']`:
|
|
2775
|
+
*
|
|
2776
|
+
* ```
|
|
2777
|
+
* // Useful so in cost explorer you can break down the costs by inference profile
|
|
2778
|
+
* component: ${profileName}InferenceProfile
|
|
2779
|
+
*
|
|
2780
|
+
* // Useful so in cost explorer you can break down the costs by component
|
|
2781
|
+
* component: ${componentName}
|
|
2782
|
+
* ```
|
|
2783
|
+
*
|
|
2784
|
+
* @since 0.14.0
|
|
2785
|
+
*/
|
|
2786
|
+
componentTagNames?: string[];
|
|
2771
2787
|
};
|
|
2772
2788
|
}
|
|
2773
2789
|
/**
|