@pulumi/ec 1.0.0-alpha.1783667091 → 1.0.0-alpha.1783683827

package/deployment.d.ts

@@ -83,7 +83,7 @@ export declare class Deployment extends pulumi.CustomResource {
      * Password for authenticating to the Elasticsearch resource.
      *
      * > **Note on deployment credentials** The <code>elastic</code> user credentials are only available whilst creating a deployment. Importing a deployment will not import the <code>elasticsearch_username</code> or <code>elasticsearch_password</code> attributes.
-     * > **Note on deployment credentials in state** The <code>elastic</code> user credentials are stored in the state file as plain text. Please follow the official Terraform recommendations regarding senstaive data in state.
+     * **Note on deployment credentials in state** The <code>elastic</code> user credentials are stored in the state file as plain text. Please follow the official Terraform recommendations regarding senstaive data in state.
      */
     readonly elasticsearchPassword: pulumi.Output<string>;
     /**
@@ -114,7 +114,7 @@ export declare class Deployment extends pulumi.CustomResource {
      * When set to true, the deployment will be updated according to the latest deployment template values.
      *
      * > **Note** If the <code>instance_configuration_id</code> or <code>instance_configuration_version</code> fields are set for a specific topology element, that element will not be updated.
-     * > **Note** Hardware migrations are not supported for deployments with node types. To use this field, the deployment needs to be migrated to node roles first.
+     * **Note** Hardware migrations are not supported for deployments with node types. To use this field, the deployment needs to be migrated to node roles first.
      */
     readonly migrateToLatestHardware: pulumi.Output<boolean | undefined>;
     /**
@@ -185,7 +185,7 @@ export interface DeploymentState {
      * Password for authenticating to the Elasticsearch resource.
      *
      * > **Note on deployment credentials** The <code>elastic</code> user credentials are only available whilst creating a deployment. Importing a deployment will not import the <code>elasticsearch_username</code> or <code>elasticsearch_password</code> attributes.
-     * > **Note on deployment credentials in state** The <code>elastic</code> user credentials are stored in the state file as plain text. Please follow the official Terraform recommendations regarding senstaive data in state.
+     * **Note on deployment credentials in state** The <code>elastic</code> user credentials are stored in the state file as plain text. Please follow the official Terraform recommendations regarding senstaive data in state.
      */
     elasticsearchPassword?: pulumi.Input<string | undefined>;
     /**
@@ -216,7 +216,7 @@ export interface DeploymentState {
      * When set to true, the deployment will be updated according to the latest deployment template values.
      *
      * > **Note** If the <code>instance_configuration_id</code> or <code>instance_configuration_version</code> fields are set for a specific topology element, that element will not be updated.
-     * > **Note** Hardware migrations are not supported for deployments with node types. To use this field, the deployment needs to be migrated to node roles first.
+     * **Note** Hardware migrations are not supported for deployments with node types. To use this field, the deployment needs to be migrated to node roles first.
      */
     migrateToLatestHardware?: pulumi.Input<boolean | undefined>;
     /**
@@ -298,7 +298,7 @@ export interface DeploymentArgs {
      * When set to true, the deployment will be updated according to the latest deployment template values.
      *
      * > **Note** If the <code>instance_configuration_id</code> or <code>instance_configuration_version</code> fields are set for a specific topology element, that element will not be updated.
-     * > **Note** Hardware migrations are not supported for deployments with node types. To use this field, the deployment needs to be migrated to node roles first.
+     * **Note** Hardware migrations are not supported for deployments with node types. To use this field, the deployment needs to be migrated to node roles first.
      */
     migrateToLatestHardware?: pulumi.Input<boolean | undefined>;
     /**

package/elasticsearchProject.d.ts

@@ -72,8 +72,8 @@ export declare class ElasticsearchProject extends pulumi.CustomResource {
     /**
      * The purpose for which the hardware of this elasticsearch project is optimized. Also known as the Elasticsearch project subtype.
      *
-     * 	- The `generalPurpose` option is suitable for most search use cases. For example, it is the right profile for full-text search, sparse vectors, and dense vectors that use compression such as BBQ. It is used by default when you create projects from the UI.
-     * 	- The `vector` option is recommended only for uncompressed dense vectors (`denseVector` fields with `int4` or `int8` quantization strategies) and high dimensionality. Refer to documentation about billing dimensions for the impact to virtual compute unit (VCU) consumption.
+     *     - The `generalPurpose` option is suitable for most search use cases. For example, it is the right profile for full-text search, sparse vectors, and dense vectors that use compression such as BBQ. It is used by default when you create projects from the UI.
+     *     - The `vector` option is recommended only for uncompressed dense vectors (`denseVector` fields with `int4` or `int8` quantization strategies) and high dimensionality. Refer to documentation about billing dimensions for the impact to virtual compute unit (VCU) consumption.
      */
     readonly optimizedFor: pulumi.Output<string>;
     /**
@@ -136,8 +136,8 @@ export interface ElasticsearchProjectState {
     /**
      * The purpose for which the hardware of this elasticsearch project is optimized. Also known as the Elasticsearch project subtype.
      *
-     * 	- The `generalPurpose` option is suitable for most search use cases. For example, it is the right profile for full-text search, sparse vectors, and dense vectors that use compression such as BBQ. It is used by default when you create projects from the UI.
-     * 	- The `vector` option is recommended only for uncompressed dense vectors (`denseVector` fields with `int4` or `int8` quantization strategies) and high dimensionality. Refer to documentation about billing dimensions for the impact to virtual compute unit (VCU) consumption.
+     *     - The `generalPurpose` option is suitable for most search use cases. For example, it is the right profile for full-text search, sparse vectors, and dense vectors that use compression such as BBQ. It is used by default when you create projects from the UI.
+     *     - The `vector` option is recommended only for uncompressed dense vectors (`denseVector` fields with `int4` or `int8` quantization strategies) and high dimensionality. Refer to documentation about billing dimensions for the impact to virtual compute unit (VCU) consumption.
      */
     optimizedFor?: pulumi.Input<string | undefined>;
     /**
@@ -180,8 +180,8 @@ export interface ElasticsearchProjectArgs {
     /**
      * The purpose for which the hardware of this elasticsearch project is optimized. Also known as the Elasticsearch project subtype.
      *
-     * 	- The `generalPurpose` option is suitable for most search use cases. For example, it is the right profile for full-text search, sparse vectors, and dense vectors that use compression such as BBQ. It is used by default when you create projects from the UI.
-     * 	- The `vector` option is recommended only for uncompressed dense vectors (`denseVector` fields with `int4` or `int8` quantization strategies) and high dimensionality. Refer to documentation about billing dimensions for the impact to virtual compute unit (VCU) consumption.
+     *     - The `generalPurpose` option is suitable for most search use cases. For example, it is the right profile for full-text search, sparse vectors, and dense vectors that use compression such as BBQ. It is used by default when you create projects from the UI.
+     *     - The `vector` option is recommended only for uncompressed dense vectors (`denseVector` fields with `int4` or `int8` quantization strategies) and high dimensionality. Refer to documentation about billing dimensions for the impact to virtual compute unit (VCU) consumption.
      */
     optimizedFor?: pulumi.Input<string | undefined>;
     /**

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@pulumi/ec",
-    "version": "1.0.0-alpha.1783667091",
+    "version": "1.0.0-alpha.1783683827",
     "description": "A Pulumi package for creating and managing ElasticCloud resources.",
     "keywords": [
         "pulumi",
@@ -27,6 +27,6 @@
     "pulumi": {
         "resource": true,
         "name": "ec",
-        "version": "1.0.0-alpha.1783667091"
+        "version": "1.0.0-alpha.1783683827"
     }
 }