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: README.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,7 +71,7 @@ To authenticate, you will need a [service account](https://docs.stackit.cloud/st
71
71
72
72
When setting up authentication, the provider will always try to use the key flow first and search for credentials in several locations, following a specific order:
73
73
74
-
1. Explicit configuration, e.g. by setting the field `service_account_key_path` in the provider block (see example below)
74
+
1. Explicit configuration, e.g. by setting the field `serviceAccountKeyPath` in the provider block
75
75
2. Environment variable, e.g. by setting `STACKIT_SERVICE_ACCOUNT_KEY_PATH` or `STACKIT_SERVICE_ACCOUNT_KEY`
76
76
3. Credentials file
77
77
@@ -127,15 +127,15 @@ To configure the key flow, follow this steps:
127
127
128
128
3. Configure the service account key for authentication in the provider by following one of the alternatives below:
129
129
130
-
- setting the fields in the provider block: `service_account_key` or `service_account_key_path`
130
+
- setting the fields in the provider block: `serviceAccountKey` or `serviceAccountKeyPath`
131
131
- setting the environment variable: `STACKIT_SERVICE_ACCOUNT_KEY_PATH` or `STACKIT_SERVICE_ACCOUNT_KEY`
132
132
- ensure the set the service account key in `STACKIT_SERVICE_ACCOUNT_KEY` is correctly formatted. Use e.g.
- setting `STACKIT_SERVICE_ACCOUNT_KEY_PATH` in the credentials file (see above)
135
135
136
136
> **Optionally, only if you have provided your own RSA key-pair when creating the service account key**, you also need to configure your private key (takes precedence over the one included in the service account key, if present). **The private key must be PEM encoded** and can be provided using one of the options below:
137
137
>
138
-
> - setting the field in the provider block: `private_key` or `private_key_path`
138
+
> - setting the field in the provider block: `privateKey` or `privateKeyPath`
139
139
> - setting the environment variable: `STACKIT_PRIVATE_KEY_PATH` or `STACKIT_PRIVATE_KEY`
140
140
> - setting `STACKIT_PRIVATE_KEY_PATH` in the credentials file (see above)
141
141
@@ -146,7 +146,7 @@ To use beta resources in the STACKIT Pulumi provider, follow these steps:
146
146
147
147
1.**Provider Configuration Option**
148
148
149
-
Set the `enable_beta_resources` option in the provider configuration. This is a boolean attribute that can be either `true` or `false`. This can be done either in code directly or via the `pulumi config` command which writes this to a Pulumi.yaml file (e.g. `pulumi config set stackit:experiments [\"routing-tables\"]`).
149
+
Set the `enableBetaResources` option in the provider configuration. This is a boolean attribute that can be either `true` or `false`. This can be done either in code directly or via the `pulumi config` command which writes this to a Pulumi.yaml file (e.g. `pulumi config set stackit:experiments [\"routing-tables\"]`).
150
150
151
151
The examples folder provides the information how this can be done in code.
152
152
@@ -158,7 +158,7 @@ To use beta resources in the STACKIT Pulumi provider, follow these steps:
158
158
export STACKIT_TF_ENABLE_BETA_RESOURCES=true
159
159
```
160
160
161
-
> **Note**: 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.
161
+
> **Note**: 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 `enableBetaResources` option specified in the provider configuration.
0 commit comments