Skip to content

Commit ba90fcf

Browse files
committed
Fixed tabpanes
1 parent a22086e commit ba90fcf

File tree

2 files changed

+21
-21
lines changed

2 files changed

+21
-21
lines changed

content/en/imt/docs/monitoring-as-code/terraform.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -22,21 +22,21 @@ Full documentation for the Splunk Terraform Provider is available [here](https:/
2222
Remaining in your AWS/EC2 instance, change into the `o11y-cloud-jumpstart` directory
2323

2424
{{< tabpane >}}
25-
{{< tab header="Change directory" lang="bash" >}}
25+
{{< tab header="Change directory" lang="sh" >}}
2626
cd observability-content-contrib/integration-examples/terraform-jumpstart
2727
{{</tab >}}
2828
{{< /tabpane >}}
2929

3030
The environment variables needed should already be set from [Installation using Helm](../../../otel/k3s/#2-installation-using-helm). If not, create the following environment variables to use in the Terraform steps below
3131

3232
{{< tabpane >}}
33-
{{< tab header="Export ACCESS TOKEN" lang="bash" >}}
33+
{{< tab header="Export ACCESS TOKEN" lang="sh" >}}
3434
export ACCESS_TOKEN="<replace_with_O11y-Workshop-ACCESS_TOKEN>"
3535
{{< /tab >}}
3636
{{< /tabpane >}}
3737

3838
{{< tabpane >}}
39-
{{< tab header="Export REALM" lang="bash" >}}
39+
{{< tab header="Export REALM" lang="sh" >}}
4040
export REALM="<replace_with_REALM>"
4141
{{< /tab >}}
4242
{{< /tabpane >}}
@@ -48,7 +48,7 @@ You will need to run the command below each time a new version of the Splunk Ter
4848
{{% /alert %}}
4949

5050
{{< tabpane >}}
51-
{{< tab header="Initialise Terraform" lang="bash" >}}
51+
{{< tab header="Initialise Terraform" lang="sh" >}}
5252
terraform init -upgrade
5353
{{</tab >}}
5454
{{< tab header="Initialise Output" lang="text" >}}
@@ -104,10 +104,10 @@ The `terraform plan` command creates an execution plan. By default, creating a p
104104
The plan command alone will not actually carry out the proposed changes, and so you can use this command to check whether the proposed changes match what you expected before you apply the changes
105105

106106
{{< tabpane >}}
107-
{{< tab header="Execution Plan" lang="bash" >}}
107+
{{< tab header="Execution Plan" lang="sh" >}}
108108
terraform plan -var="access_token=$ACCESS_TOKEN" -var="realm=$REALM" -var="o11y_prefix=[$(hostname)]"
109109
{{</tab >}}
110-
{{< tab header="Execution Plan Output" lang="bash" >}}
110+
{{< tab header="Execution Plan Output" lang="text" >}}
111111
Plan: 146 to add, 0 to change, 0 to destroy.
112112
{{</tab >}}
113113
{{< /tabpane >}}
@@ -125,18 +125,18 @@ The most straightforward way to use `terraform apply` is to run it without any a
125125
Due to this being a workshop it is required that the prefix is to be unique so you need to run the `terraform apply` below.
126126

127127
{{< tabpane >}}
128-
{{< tab header="Apply Plan" lang="bash" >}}
128+
{{< tab header="Apply Plan" lang="sh" >}}
129129
terraform apply -var="access_token=$ACCESS_TOKEN" -var="realm=$REALM" -var="o11y_prefix=[$(hostname)]"
130130
{{</tab >}}
131-
{{< tab header="Apply Plan Output" lang="bash" >}}
131+
{{< tab header="Apply Plan Output" lang="text" >}}
132132
Apply complete! Resources: 146 added, 0 changed, 0 destroyed.
133133
{{</tab >}}
134134
{{< /tabpane >}}
135135

136136
Once the apply has completed, validate that the detectors were created, under the **Alerts & Detectors** and click on the **Detectors** tab. They will be prefixed by the hostname of your instance. To check the prefix value run:
137137

138138
{{< tabpane >}}
139-
{{< tab header="Echo Hostname" lang="bash" >}}
139+
{{< tab header="Echo Hostname" lang="sh" >}}
140140
echo $(hostname)
141141
{{</tab >}}
142142
{{< /tabpane >}}
@@ -154,10 +154,10 @@ While you will typically not want to destroy long-lived objects in a production
154154
Now go and destroy all the Detectors and Dashboards that were previously applied!
155155

156156
{{< tabpane >}}
157-
{{< tab header="Destroy" lang="bash" >}}
157+
{{< tab header="Destroy" lang="sh" >}}
158158
terraform destroy -var="access_token=$ACCESS_TOKEN" -var="realm=$REALM"
159159
{{</tab >}}
160-
{{< tab header="Destroy Output" lang="bash" >}}
160+
{{< tab header="Destroy Output" lang="text" >}}
161161
Destroy complete! Resources: 146 destroyed.
162162
{{</tab >}}
163163
{{< /tabpane >}}

content/ja/imt/docs/monitoring-as-code/terraform.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -23,15 +23,15 @@ Splunk Terraform Providerの完全なドキュメントは[こちら](https://re
2323
AWS/EC2 インスタンスにログインして、`o11y-cloud-jumpstart` ディレクトリに移動します
2424

2525
{{< tabpane >}}
26-
{{< tab header="Change directory" lang="bash" >}}
26+
{{< tab header="Change directory" lang="sh" >}}
2727
cd observability-content-contrib/integration-examples/terraform-jumpstart
2828
{{</tab >}}
2929
{{< /tabpane >}}
3030

3131
必要な環境変数は、[Helmによるインストール](../../gdi/k3s/#2-helm%E3%81%AB%E3%82%88%E3%82%8B%E3%82%A4%E3%83%B3%E3%82%B9%E3%83%88%E3%83%BC%E3%83%AB) ですでに設定されているはずです。そうでない場合は、以下の Terraform のステップで使用するために、以下の環境変数を作成してください。
3232

3333
{{< tabpane >}}
34-
{{< tab header="Environment Variables" lang="bash" >}}
34+
{{< tab header="Environment Variables" lang="sh" >}}
3535
export ACCESS_TOKEN=<replace_with_O11y-Workshop-ACCESS_token>
3636
export REALM=<replace_with_splunk_realm>
3737
{{</tab >}}
@@ -44,7 +44,7 @@ Splunk Terraform Provider の新バージョンがリリースされるたびに
4444
{{% /alert %}}
4545

4646
{{< tabpane >}}
47-
{{< tab header="Initialise Terraform" lang="bash" >}}
47+
{{< tab header="Initialise Terraform" lang="sh" >}}
4848
terraform init -upgrade
4949
{{</tab >}}
5050
{{< tab header="Initialise Output" lang="text" >}}
@@ -100,10 +100,10 @@ terraform init -upgrade
100100
plan コマンドだけでは、提案された変更を実際に実行はされなません。変更を適用する前に、以下のコマンドを実行して、提案された変更が期待したものと一致するかどうかを確認しましょう。
101101

102102
{{< tabpane >}}
103-
{{< tab header="Execution Plan" lang="bash" >}}
103+
{{< tab header="Execution Plan" lang="sh" >}}
104104
terraform plan -var="access_token=$ACCESS_TOKEN" -var="realm=$REALM" -var="sfx_prefix=[$(hostname)]"
105105
{{</tab >}}
106-
{{< tab header="Execution Plan Output" lang="bash" >}}
106+
{{< tab header="Execution Plan Output" lang="text" >}}
107107
Plan: 146 to add, 0 to change, 0 to destroy.
108108
{{</tab >}}
109109
{{< /tabpane >}}
@@ -121,18 +121,18 @@ Plan: 146 to add, 0 to change, 0 to destroy.
121121
このワークショップでは、プレフィックスがユニークである必要があります。以下の `terraform apply` を実行してください。
122122

123123
{{< tabpane >}}
124-
{{< tab header="Apply Plan" lang="bash" >}}
124+
{{< tab header="Apply Plan" lang="sh" >}}
125125
terraform apply -var="access_token=$ACCESS_TOKEN" -var="realm=$REALM" -var="sfx_prefix=[$(hostname)]"
126126
{{</tab >}}
127-
{{< tab header="Apply Plan Output" lang="bash" >}}
127+
{{< tab header="Apply Plan Output" lang="text" >}}
128128
Apply complete! Resources: 146 added, 0 changed, 0 destroyed.
129129
{{</tab >}}
130130
{{< /tabpane >}}
131131

132132
適用が完了したら、 **Alerts → Detectors** でディテクターが作成されたことを確認してください。ディテクターのプレフィックスには、インスタンスのホスト名が入ります。プレフィックスの値を確認するには以下を実行してください。
133133

134134
{{< tabpane >}}
135-
{{< tab header="Echo Hostname" lang="bash" >}}
135+
{{< tab header="Echo Hostname" lang="sh" >}}
136136
echo $(hostname)
137137
{{</tab >}}
138138
{{< /tabpane >}}
@@ -150,10 +150,10 @@ echo $(hostname)
150150
それでは、ここまでで適用したダッシュボードとディテクターを全て破壊しましょう!
151151

152152
{{< tabpane >}}
153-
{{< tab header="Destroy" lang="bash" >}}
153+
{{< tab header="Destroy" lang="sh" >}}
154154
terraform destroy -var="access_token=$ACCESS_TOKEN" -var="realm=$REALM"
155155
{{</tab >}}
156-
{{< tab header="Destroy Output" lang="bash" >}}
156+
{{< tab header="Destroy Output" lang="text" >}}
157157
Destroy complete! Resources: 146 destroyed.
158158
{{</tab >}}
159159
{{< /tabpane >}}

0 commit comments

Comments
 (0)