Merge pull request #40 from sematext/develop

Develop

README.md

@@ -50,6 +50,8 @@ provider "sematext" {
 resource "sematext_monitor_elasticsearch" "mymonitor" {
     name = "Node.js Monitor Example"
     billing_plan_id = 12
+    apptoken_name = "my apptoken name"
+    apptoken_create_missing = true
 }
 ```
 

docs/index.md

@@ -12,7 +12,7 @@ terraform {
   required_providers {
     sematext = {
       source = "sematext/sematext"
-      version = ">=0.1.9"
+      version = ">=0.1.3"
     }
   }
 }

docs/resources/sematext_monitor_akka.md

@@ -24,17 +24,32 @@ provider "sematext" {
 resource "sematext_monitor_akka" "mymonitor" {
   name = "my monitor name"
   billing_plan_id = <[plan id](../guides/plans.md)>
+  apptoken {
+    name "my apptoken name"
+    create_missing true
+  }
 }
 ```
 
 ## Argument Reference
 
-* `name` - List attributes that this resource exports.
-* `billing_plan_id` - List attributes that this resource exports. [Refer to plan guidance for list of legal values](../guides/plans.md)
+* `name` - List attributes that this resource exports;
+* `billing_plan_id` - List attributes that this resource exports. [Refer to plan guidance for list of legal values](../guides/plans.md);
+* `apptoken.name` - Refer note below;
+
+
+## App-tokens
+
+Sematext Cloud Apps have one or more apptokens. These app-tokens are named and have an id issued on creation.
+This is so that downstream resources can be grouped, with the instances within each group using the same app-token.
 
+Within Terraform state the apptoken.id is a calculated value, issued by Sematext Cloud.
+When provisioning, downstream resources should set the app-token id in their configuration.
 
+To prevent redeployment of downstream resources on change to apptokens we recommend using [null resource provider](https://registry.terraform.io/providers/hashicorp/null/latest/docs/resources/resource)
+to handle the provisioning.
 
 ## Outputs
 
 * `id` - The app id. Provided on creation and used in terraform destroy operations.
-* `token` - On creation of the resource an app-token is generated for re-use in configuration of collection agents.
+* `apptoken.id` - On creation of the resource an app-token is generated for re-use in configuration of APM / collectors.

docs/resources/sematext_monitor_apache.md

@@ -24,17 +24,32 @@ provider "sematext" {
 resource "sematext_monitor_apache" "mymonitor" {
   name = "my monitor name"
   billing_plan_id = <[plan id](../guides/plans.md)>
+  apptoken {
+    name "my apptoken name"
+    create_missing true
+  }
 }
 ```
 
 ## Argument Reference
 
-* `name` - List attributes that this resource exports.
-* `billing_plan_id` - List attributes that this resource exports. [Refer to plan guidance for list of legal values](../guides/plans.md)
+* `name` - List attributes that this resource exports;
+* `billing_plan_id` - List attributes that this resource exports. [Refer to plan guidance for list of legal values](../guides/plans.md);
+* `apptoken.name` - Refer note below;
+
+
+## App-tokens
+
+Sematext Cloud Apps have one or more apptokens. These app-tokens are named and have an id issued on creation.
+This is so that downstream resources can be grouped, with the instances within each group using the same app-token.
 
+Within Terraform state the apptoken.id is a calculated value, issued by Sematext Cloud.
+When provisioning, downstream resources should set the app-token id in their configuration.
 
+To prevent redeployment of downstream resources on change to apptokens we recommend using [null resource provider](https://registry.terraform.io/providers/hashicorp/null/latest/docs/resources/resource)
+to handle the provisioning.
 
 ## Outputs
 
 * `id` - The app id. Provided on creation and used in terraform destroy operations.
-* `token` - On creation of the resource an app-token is generated for re-use in configuration of collection agents.
+* `apptoken.id` - On creation of the resource an app-token is generated for re-use in configuration of APM / collectors.

docs/resources/sematext_monitor_awsebs.md

@@ -24,20 +24,35 @@ provider "sematext" {
 resource "sematext_monitor_awsebs" "mymonitor" {
   name = "my monitor name"
   billing_plan_id = <[plan id](../guides/plans.md)>
+  apptoken {
+    name "my apptoken name"
+    create_missing true
+  }
 }
 ```
 
 ## Argument Reference
 
-* `name` - List attributes that this resource exports.
-* `billing_plan_id` - List attributes that this resource exports. [Refer to plan guidance for list of legal values](../guides/plans.md)
+* `name` - List attributes that this resource exports;
+* `billing_plan_id` - List attributes that this resource exports. [Refer to plan guidance for list of legal values](../guides/plans.md);
+* `apptoken.name` - Refer note below;
 * `aws_access_key` - (optional) if not set then reads from env AWS_ACCESS_KEY_ID.
 * `aws_secret_key` - (optionl) is not present set from env AWS_SECRET_ACCESS_KEY
 * `aws_fetch_frequency` - (required) one of MINUTE|FIVE_MINUTES|FIFTEEN_MINUTES.
 * `aws_region` - (optional) if not present withh set from env AWS_REGION.
 
+## App-tokens
+
+Sematext Cloud Apps have one or more apptokens. These app-tokens are named and have an id issued on creation.
+This is so that downstream resources can be grouped, with the instances within each group using the same app-token.
+
+Within Terraform state the apptoken.id is a calculated value, issued by Sematext Cloud.
+When provisioning, downstream resources should set the app-token id in their configuration.
+
+To prevent redeployment of downstream resources on change to apptokens we recommend using [null resource provider](https://registry.terraform.io/providers/hashicorp/null/latest/docs/resources/resource)
+to handle the provisioning.
 
 ## Outputs
 
 * `id` - The app id. Provided on creation and used in terraform destroy operations.
-* `token` - On creation of the resource an app-token is generated for re-use in configuration of collection agents.
+* `apptoken.id` - On creation of the resource an app-token is generated for re-use in configuration of APM / collectors.

docs/resources/sematext_monitor_awsec2.md

@@ -24,20 +24,35 @@ provider "sematext" {
 resource "sematext_monitor_awsec2" "mymonitor" {
   name = "my monitor name"
   billing_plan_id = <[plan id](../guides/plans.md)>
+  apptoken {
+    name "my apptoken name"
+    create_missing true
+  }
 }
 ```
 
 ## Argument Reference
 
-* `name` - List attributes that this resource exports.
-* `billing_plan_id` - List attributes that this resource exports. [Refer to plan guidance for list of legal values](../guides/plans.md)
+* `name` - List attributes that this resource exports;
+* `billing_plan_id` - List attributes that this resource exports. [Refer to plan guidance for list of legal values](../guides/plans.md);
+* `apptoken.name` - Refer note below;
 * `aws_access_key` - (optional) if not set then reads from env AWS_ACCESS_KEY_ID.
 * `aws_secret_key` - (optionl) is not present set from env AWS_SECRET_ACCESS_KEY
 * `aws_fetch_frequency` - (required) one of MINUTE|FIVE_MINUTES|FIFTEEN_MINUTES.
 * `aws_region` - (optional) if not present withh set from env AWS_REGION.
 
+## App-tokens
+
+Sematext Cloud Apps have one or more apptokens. These app-tokens are named and have an id issued on creation.
+This is so that downstream resources can be grouped, with the instances within each group using the same app-token.
+
+Within Terraform state the apptoken.id is a calculated value, issued by Sematext Cloud.
+When provisioning, downstream resources should set the app-token id in their configuration.
+
+To prevent redeployment of downstream resources on change to apptokens we recommend using [null resource provider](https://registry.terraform.io/providers/hashicorp/null/latest/docs/resources/resource)
+to handle the provisioning.
 
 ## Outputs
 
 * `id` - The app id. Provided on creation and used in terraform destroy operations.
-* `token` - On creation of the resource an app-token is generated for re-use in configuration of collection agents.
+* `apptoken.id` - On creation of the resource an app-token is generated for re-use in configuration of APM / collectors.

docs/resources/sematext_monitor_awselb.md

@@ -24,20 +24,35 @@ provider "sematext" {
 resource "sematext_monitor_awselb" "mymonitor" {
   name = "my monitor name"
   billing_plan_id = <[plan id](../guides/plans.md)>
+  apptoken {
+    name "my apptoken name"
+    create_missing true
+  }
 }
 ```
 
 ## Argument Reference
 
-* `name` - List attributes that this resource exports.
-* `billing_plan_id` - List attributes that this resource exports. [Refer to plan guidance for list of legal values](../guides/plans.md)
+* `name` - List attributes that this resource exports;
+* `billing_plan_id` - List attributes that this resource exports. [Refer to plan guidance for list of legal values](../guides/plans.md);
+* `apptoken.name` - Refer note below;
 * `aws_access_key` - (optional) if not set then reads from env AWS_ACCESS_KEY_ID.
 * `aws_secret_key` - (optionl) is not present set from env AWS_SECRET_ACCESS_KEY
 * `aws_fetch_frequency` - (required) one of MINUTE|FIVE_MINUTES|FIFTEEN_MINUTES.
 * `aws_region` - (optional) if not present withh set from env AWS_REGION.
 
+## App-tokens
+
+Sematext Cloud Apps have one or more apptokens. These app-tokens are named and have an id issued on creation.
+This is so that downstream resources can be grouped, with the instances within each group using the same app-token.
+
+Within Terraform state the apptoken.id is a calculated value, issued by Sematext Cloud.
+When provisioning, downstream resources should set the app-token id in their configuration.
+
+To prevent redeployment of downstream resources on change to apptokens we recommend using [null resource provider](https://registry.terraform.io/providers/hashicorp/null/latest/docs/resources/resource)
+to handle the provisioning.
 
 ## Outputs
 
 * `id` - The app id. Provided on creation and used in terraform destroy operations.
-* `token` - On creation of the resource an app-token is generated for re-use in configuration of collection agents.
+* `apptoken.id` - On creation of the resource an app-token is generated for re-use in configuration of APM / collectors.

docs/resources/sematext_monitor_cassandra.md

@@ -24,17 +24,32 @@ provider "sematext" {
 resource "sematext_monitor_cassandra" "mymonitor" {
   name = "my monitor name"
   billing_plan_id = <[plan id](../guides/plans.md)>
+  apptoken {
+    name "my apptoken name"
+    create_missing true
+  }
 }
 ```
 
 ## Argument Reference
 
-* `name` - List attributes that this resource exports.
-* `billing_plan_id` - List attributes that this resource exports. [Refer to plan guidance for list of legal values](../guides/plans.md)
+* `name` - List attributes that this resource exports;
+* `billing_plan_id` - List attributes that this resource exports. [Refer to plan guidance for list of legal values](../guides/plans.md);
+* `apptoken.name` - Refer note below;
+
+
+## App-tokens
+
+Sematext Cloud Apps have one or more apptokens. These app-tokens are named and have an id issued on creation.
+This is so that downstream resources can be grouped, with the instances within each group using the same app-token.
 
+Within Terraform state the apptoken.id is a calculated value, issued by Sematext Cloud.
+When provisioning, downstream resources should set the app-token id in their configuration.
 
+To prevent redeployment of downstream resources on change to apptokens we recommend using [null resource provider](https://registry.terraform.io/providers/hashicorp/null/latest/docs/resources/resource)
+to handle the provisioning.
 
 ## Outputs
 
 * `id` - The app id. Provided on creation and used in terraform destroy operations.
-* `token` - On creation of the resource an app-token is generated for re-use in configuration of collection agents.
+* `apptoken.id` - On creation of the resource an app-token is generated for re-use in configuration of APM / collectors.

docs/resources/sematext_monitor_clickhouse.md

@@ -24,17 +24,32 @@ provider "sematext" {
 resource "sematext_monitor_clickhouse" "mymonitor" {
   name = "my monitor name"
   billing_plan_id = <[plan id](../guides/plans.md)>
+  apptoken {
+    name "my apptoken name"
+    create_missing true
+  }
 }
 ```
 
 ## Argument Reference
 
-* `name` - List attributes that this resource exports.
-* `billing_plan_id` - List attributes that this resource exports. [Refer to plan guidance for list of legal values](../guides/plans.md)
+* `name` - List attributes that this resource exports;
+* `billing_plan_id` - List attributes that this resource exports. [Refer to plan guidance for list of legal values](../guides/plans.md);
+* `apptoken.name` - Refer note below;
+
+
+## App-tokens
+
+Sematext Cloud Apps have one or more apptokens. These app-tokens are named and have an id issued on creation.
+This is so that downstream resources can be grouped, with the instances within each group using the same app-token.
 
+Within Terraform state the apptoken.id is a calculated value, issued by Sematext Cloud.
+When provisioning, downstream resources should set the app-token id in their configuration.
 
+To prevent redeployment of downstream resources on change to apptokens we recommend using [null resource provider](https://registry.terraform.io/providers/hashicorp/null/latest/docs/resources/resource)
+to handle the provisioning.
 
 ## Outputs
 
 * `id` - The app id. Provided on creation and used in terraform destroy operations.
-* `token` - On creation of the resource an app-token is generated for re-use in configuration of collection agents.
+* `apptoken.id` - On creation of the resource an app-token is generated for re-use in configuration of APM / collectors.

docs/resources/sematext_monitor_elasticsearch.md

@@ -24,17 +24,32 @@ provider "sematext" {
 resource "sematext_monitor_elasticsearch" "mymonitor" {
   name = "my monitor name"
   billing_plan_id = <[plan id](../guides/plans.md)>
+  apptoken {
+    name "my apptoken name"
+    create_missing true
+  }
 }
 ```
 
 ## Argument Reference
 
-* `name` - List attributes that this resource exports.
-* `billing_plan_id` - List attributes that this resource exports. [Refer to plan guidance for list of legal values](../guides/plans.md)
+* `name` - List attributes that this resource exports;
+* `billing_plan_id` - List attributes that this resource exports. [Refer to plan guidance for list of legal values](../guides/plans.md);
+* `apptoken.name` - Refer note below;
+
+
+## App-tokens
+
+Sematext Cloud Apps have one or more apptokens. These app-tokens are named and have an id issued on creation.
+This is so that downstream resources can be grouped, with the instances within each group using the same app-token.
 
+Within Terraform state the apptoken.id is a calculated value, issued by Sematext Cloud.
+When provisioning, downstream resources should set the app-token id in their configuration.
 
+To prevent redeployment of downstream resources on change to apptokens we recommend using [null resource provider](https://registry.terraform.io/providers/hashicorp/null/latest/docs/resources/resource)
+to handle the provisioning.
 
 ## Outputs
 
 * `id` - The app id. Provided on creation and used in terraform destroy operations.
-* `token` - On creation of the resource an app-token is generated for re-use in configuration of collection agents.
+* `apptoken.id` - On creation of the resource an app-token is generated for re-use in configuration of APM / collectors.

docs/resources/sematext_monitor_hadoopmrv1.md

@@ -24,17 +24,32 @@ provider "sematext" {
 resource "sematext_monitor_hadoopmrv1" "mymonitor" {
   name = "my monitor name"
   billing_plan_id = <[plan id](../guides/plans.md)>
+  apptoken {
+    name "my apptoken name"
+    create_missing true
+  }
 }
 ```
 
 ## Argument Reference
 
-* `name` - List attributes that this resource exports.
-* `billing_plan_id` - List attributes that this resource exports. [Refer to plan guidance for list of legal values](../guides/plans.md)
+* `name` - List attributes that this resource exports;
+* `billing_plan_id` - List attributes that this resource exports. [Refer to plan guidance for list of legal values](../guides/plans.md);
+* `apptoken.name` - Refer note below;
+
+
+## App-tokens
+
+Sematext Cloud Apps have one or more apptokens. These app-tokens are named and have an id issued on creation.
+This is so that downstream resources can be grouped, with the instances within each group using the same app-token.
 
+Within Terraform state the apptoken.id is a calculated value, issued by Sematext Cloud.
+When provisioning, downstream resources should set the app-token id in their configuration.
 
+To prevent redeployment of downstream resources on change to apptokens we recommend using [null resource provider](https://registry.terraform.io/providers/hashicorp/null/latest/docs/resources/resource)
+to handle the provisioning.
 
 ## Outputs
 
 * `id` - The app id. Provided on creation and used in terraform destroy operations.
-* `token` - On creation of the resource an app-token is generated for re-use in configuration of collection agents.
+* `apptoken.id` - On creation of the resource an app-token is generated for re-use in configuration of APM / collectors.

docs/resources/sematext_monitor_hadoopyarn.md

@@ -24,17 +24,32 @@ provider "sematext" {
 resource "sematext_monitor_hadoopyarn" "mymonitor" {
   name = "my monitor name"
   billing_plan_id = <[plan id](../guides/plans.md)>
+  apptoken {
+    name "my apptoken name"
+    create_missing true
+  }
 }
 ```
 
 ## Argument Reference
 
-* `name` - List attributes that this resource exports.
-* `billing_plan_id` - List attributes that this resource exports. [Refer to plan guidance for list of legal values](../guides/plans.md)
+* `name` - List attributes that this resource exports;
+* `billing_plan_id` - List attributes that this resource exports. [Refer to plan guidance for list of legal values](../guides/plans.md);
+* `apptoken.name` - Refer note below;
+
+
+## App-tokens
+
+Sematext Cloud Apps have one or more apptokens. These app-tokens are named and have an id issued on creation.
+This is so that downstream resources can be grouped, with the instances within each group using the same app-token.
 
+Within Terraform state the apptoken.id is a calculated value, issued by Sematext Cloud.
+When provisioning, downstream resources should set the app-token id in their configuration.
 
+To prevent redeployment of downstream resources on change to apptokens we recommend using [null resource provider](https://registry.terraform.io/providers/hashicorp/null/latest/docs/resources/resource)
+to handle the provisioning.
 
 ## Outputs
 
 * `id` - The app id. Provided on creation and used in terraform destroy operations.
-* `token` - On creation of the resource an app-token is generated for re-use in configuration of collection agents.
+* `apptoken.id` - On creation of the resource an app-token is generated for re-use in configuration of APM / collectors.