You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guides/opting_into_beta_resources.md
+7-11Lines changed: 7 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,17 +3,17 @@ page_title: "Configuring Beta Resources in the STACKIT Terraform Provider"
3
3
---
4
4
# Configuring Beta Resources in the STACKIT Terraform Provider
5
5
6
-
###Overview
6
+
## Overview
7
7
8
8
This guide explains how to opt into beta resources within the STACKIT Terraform provider. Beta resources are new services and features from STACKIT that are still in development and might not yet have a stable API.
9
9
10
10
Opting into beta functionality allows users to experiment with new features and services before their official release, without compromising the stability of other resources and the provider itself. However, it's important to remember that beta resources may not be as stable as fully released counterparts, so use them with caution and provide feedback to help improve these services.
11
11
12
-
###The Process of Opting into the Beta
12
+
## The Process of Opting into the Beta
13
13
14
14
To use beta resources in the STACKIT Terraform provider, you have two options:
15
15
16
-
####Option 1: Provider Configuration
16
+
### Option 1: Provider Configuration
17
17
18
18
Set the `enable_beta_resources` option in the provider configuration. This is a boolean attribute that can be either `true` or `false`.
19
19
@@ -24,20 +24,16 @@ provider "stackit" {
24
24
}
25
25
```
26
26
27
-
####Option 2: Environment Variable
27
+
### Option 2: Environment Variable
28
28
29
29
Set the `STACKIT_TF_ENABLE_BETA_RESOURCES` environment variable to `"true"` or `"false"`. Other values will be ignored and will produce a warning.
30
30
31
31
```sh
32
32
export STACKIT_TF_ENABLE_BETA_RESOURCES=true
33
33
```
34
34
35
-
> **Note**: **The environment variable takes precedence over the provider configuration option.**
36
-
>
37
-
> This means that if the `STACKIT_TF_ENABLE_BETA_RESOURCES` environment variable is set to a valid value (`"true"` or `"false"`), it will override the `enable_beta_resources` option specified in the provider configuration.
35
+
-> The environment variable takes precedence over the provider configuration option. This means that if the `STACKIT_TF_ENABLE_BETA_RESOURCES` environment variable is set to a valid value (`"true"` or `"false"`), it will override the `enable_beta_resources` option specified in the provider configuration.
38
36
39
-
###Listing Beta Resources
37
+
## Listing Beta Resources
40
38
41
-
Currently, there are no beta resources available. This section will be updated as new beta services are introduced.
42
-
43
-
> **Tip**: Check back regularly or refer to the [STACKIT provider documentation](#) for the latest updates on beta resources.
39
+
Currently, there are no beta resources available. This section will be updated as new beta services are introduced.
# Using Vault Provider with STACKIT Secrets Manager
5
5
6
-
###Overview
6
+
## Overview
7
7
8
8
This guide outlines the process of utilizing the HashiCorp Vault provider alongside the STACKIT provider to write secrets in the STACKIT Secrets Manager. The guide focuses on secrets from STACKIT Cloud resources but can be adapted for any secret.
9
9
10
-
###Steps
10
+
## Steps
11
11
12
12
1.**Configure STACKIT Provider**
13
13
@@ -78,6 +78,6 @@ This guide outlines the process of utilizing the HashiCorp Vault provider alongs
78
78
}
79
79
```
80
80
81
-
### Note
81
+
## Note
82
82
83
83
This example can be adapted for various resources within the provider as well as any other Secret the user wants to set in the Secrets Manager instance. Adapting this examples means replacing the Argus Monitoring Grafana password with the appropriate value.
Copy file name to clipboardExpand all lines: templates/guides/opting_into_beta_resources.md.tmpl
+7-11Lines changed: 7 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -3,17 +3,17 @@ page_title: "Configuring Beta Resources in the STACKIT Terraform Provider"
3
3
---
4
4
# Configuring Beta Resources in the STACKIT Terraform Provider
5
5
6
-
### Overview
6
+
## Overview
7
7
8
8
This guide explains how to opt into beta resources within the STACKIT Terraform provider. Beta resources are new services and features from STACKIT that are still in development and might not yet have a stable API.
9
9
10
10
Opting into beta functionality allows users to experiment with new features and services before their official release, without compromising the stability of other resources and the provider itself. However, it's important to remember that beta resources may not be as stable as fully released counterparts, so use them with caution and provide feedback to help improve these services.
11
11
12
-
### The Process of Opting into the Beta
12
+
## The Process of Opting into the Beta
13
13
14
14
To use beta resources in the STACKIT Terraform provider, you have two options:
15
15
16
-
#### Option 1: Provider Configuration
16
+
### Option 1: Provider Configuration
17
17
18
18
Set the `enable_beta_resources` option in the provider configuration. This is a boolean attribute that can be either `true`or`false`.
19
19
@@ -24,20 +24,16 @@ provider "stackit" {
24
24
}
25
25
```
26
26
27
-
#### Option 2: Environment Variable
27
+
### Option 2: Environment Variable
28
28
29
29
Set the `STACKIT_TF_ENABLE_BETA_RESOURCES` environment variable to `"true"`or`"false"`. Other values will be ignored and will produce a warning.
30
30
31
31
```sh
32
32
export STACKIT_TF_ENABLE_BETA_RESOURCES=true
33
33
```
34
34
35
-
> **Note**: **The environment variable takes precedence over the provider configuration option.**
36
-
>
37
-
> This means that if the `STACKIT_TF_ENABLE_BETA_RESOURCES` environment variable is set to a valid value (`"true"`or`"false"`), it will override the `enable_beta_resources` option specified in the provider configuration.
35
+
-> The environment variable takes precedence over the provider configuration option. This means that if the `STACKIT_TF_ENABLE_BETA_RESOURCES` environment variable is set to a valid value (`"true"`or`"false"`), it will override the `enable_beta_resources` option specified in the provider configuration.
38
36
39
-
### Listing Beta Resources
37
+
## Listing Beta Resources
40
38
41
-
Currently, there are no beta resources available. This section will be updated as new beta services are introduced.
42
-
43
-
> **Tip**: Check back regularly or refer to the [STACKIT provider documentation](#) for the latest updates on beta resources.
39
+
Currently, there are no beta resources available. This section will be updated as new beta services are introduced.
# Using Vault Provider with STACKIT Secrets Manager
5
5
6
-
### Overview
6
+
## Overview
7
7
8
8
This guide outlines the process of utilizing the HashiCorp Vault provider alongside the STACKIT provider to write secrets in the STACKIT Secrets Manager. The guide focuses on secrets from STACKIT Cloud resources but can be adapted for any secret.
9
9
10
-
### Steps
10
+
## Steps
11
11
12
12
1. **Configure STACKIT Provider**
13
13
@@ -78,6 +78,6 @@ This guide outlines the process of utilizing the HashiCorp Vault provider alongs
78
78
}
79
79
```
80
80
81
-
### Note
81
+
## Note
82
82
83
83
This example can be adapted for various resources within the provider as well as any other Secret the user wants to set in the Secrets Manager instance. Adapting this examples means replacing the Argus Monitoring Grafana password with the appropriate value.
0 commit comments