Skip to content

Commit ba9d239

Browse files
committed
refresh AKS JA copy + minor edits
1 parent b841e3d commit ba9d239

File tree

5 files changed

+13
-21
lines changed

5 files changed

+13
-21
lines changed

docs/guides/integration-javascript-client-server.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -124,8 +124,6 @@ Based on the status and availability of a valid identity, the SDK does the follo
124124
1. Stores identity information in [local storage or a first-party cookie](../sdks/sdk-ref-javascript.md#uid2-storage-format).
125125
1. Uses the identity information to initiate requests for targeted advertising.
126126

127-
<!-- (**GWH_TODO. Q: Not sure about the relationship between the steps above and the table below. And the diagram 2-a which says "the publisher calls the SSP for ads using the UID2 token". A: Diagram needs to be updated.**) -->
128-
129127
The bidding step is shown in the following table.
130128

131129
| Step | Endpoint/SDK | Description |

docs/guides/integration-javascript.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ The options for integrating with UID2 using the SDK for JavaScript are summarize
3737
| Scenario | Option | Integration Guide |
3838
| :--- | :--- | :--- |
3939
| You have access to DII on the client side and want to do front-end development only. | Client-side integration | [Client-Side Integration Guide for JavaScript](integration-javascript-client-side.md) |
40-
| You have access to DII on the server side and can do server-side development, or you are using a <Link href="../ref-info/glossary-uid#gl-private-operator">Private Operator</Link>. | Server-side integration | [Client-Server Integration Guide for JavaScript](integration-javascript-client-server.md) |
40+
| You have access to DII on the server side and can do server-side development, or you are using a <Link href="../ref-info/glossary-uid#gl-private-operator">Private Operator</Link>. | Client-server integration | [Client-Server Integration Guide for JavaScript](integration-javascript-client-server.md) |
4141

4242
## Complete UID2 Account Setup and Configure Account
4343

i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-javascript-client-server.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -124,8 +124,6 @@ SDKは、指定された [callback function](../sdks/sdk-ref-javascript.md#callb
124124
1. ID 情報を [ローカルストレージまたはファーストパーティクッキー](../sdks/sdk-ref-javascript.md#uid2-storage-format) に保存します。
125125
1. ID 情報を使用して、ターゲティング広告のリクエストを始めます。
126126

127-
<!-- (**GWH_TODO. Q: Not sure about the relationship between the steps above and the table below. And the diagram 2-a which says "the publisher calls the SSP for ads using the UID2 token". A: Diagram needs to be updated.**) -->
128-
129127
ビッドステップを次の表に示します。
130128

131129
| Step | Endpoint/SDK | Description |

i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-javascript.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ SDK for JavaScript を使って UID2 とインテグレーションするため
3737
| Scenario | Option | Integration Guide |
3838
| :--- | :--- | :--- |
3939
| Client-Side で DII にアクセスでき、フロントエンド開発のみを行いたい。 | Client-side integration | [Client-Side Integration Guide for JavaScript](integration-javascript-client-side.md) |
40-
| Server-Side で DII にアクセスでき、Server-Side の開発が可能であるか、<Link href="../ref-info/glossary-uid#gl-private-operator">Private Operator</Link> を使用している。 | Server-side integration | [Client-Server Integration Guide for JavaScript](integration-javascript-client-server.md) |
40+
| Client-Server で DII にアクセスでき、Server-Side の開発が可能であるか、<Link href="../ref-info/glossary-uid#gl-private-operator">Private Operator</Link> を使用している。 | Client-server integration | [Client-Server Integration Guide for JavaScript](integration-javascript-client-server.md) |
4141

4242
## Complete UID2 Account Setup and Configure Account
4343

i18n/ja/docusaurus-plugin-content-docs/current/guides/operator-guide-aks-enclave.md

Lines changed: 11 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -92,8 +92,6 @@ To deploy a new UID2 Private Operator for AKS, you'll need to complete the follo
9292

9393
### Download ZIP File and Extract Files
9494

95-
[**KC__GWH01 I've commented out some of what we had -- it doesn't make sense to include the table unless we add AKS to the release matrix. We need to include instructions to get the file. What I'm putting here is just a guess... please fix as needed.**]
96-
9795
To get set up with the installation files, follow these steps:
9896

9997
1. Ask your UID2 contact for the ZIP file containing the deployment files.
@@ -116,8 +114,6 @@ The latest ZIP file is linked in the AKS Download column in the following table.
116114

117115
Run the following commands to prepare environment variables that you'll use later. Choose variable names to suit your needs.
118116

119-
[**KC__GWH02 do we need to say where they need to run these commands? Maybe not... just checking. At the Azure command line?**]
120-
121117
```
122118
export RESOURCE_GROUP="my-vn-aks"
123119
export LOCATION="eastus"
@@ -135,7 +131,7 @@ export DEPLOYMENT_ENV="integ"
135131

136132
### Set Up AKS and Node Pool
137133

138-
To set up AKS and the node pool, complete the following steps: [**KC__GWH03 do they have to be done in sequence? If so we could use numbers rather than bullets**]
134+
To set up AKS and the node pool, complete the following steps:
139135

140136
- [Create Resource Group](#create-resource-group)
141137
- [Create Virtual Network](#create-virtual-network)
@@ -172,7 +168,7 @@ There are some limitations with regard to location:
172168

173169
#### Create Virtual Network
174170

175-
To create the virtual network, run the following command, using your own values as needed: [**KC__GWH04 please verify the intro line/modify as needed**]
171+
To create the virtual network, run the following command, using your own values as needed:
176172

177173
```
178174
az network vnet create \
@@ -184,7 +180,7 @@ az network vnet create \
184180

185181
#### Create Subnets
186182

187-
To create the subnets, run the following command, using your own values as needed: [**KC__GWH05 please verify the intro line/modify as needed**]
183+
To create the subnets, run the following command, using your own values as needed:
188184

189185
```
190186
# Default Subnet (10.0.0.0/24)
@@ -212,15 +208,15 @@ az network vnet subnet create \
212208

213209
#### Create Public IP Address
214210

215-
To create the public IP address, run the following command, using your own values as needed: [**KC__GWH06 please verify the intro line/modify as needed**]
211+
To create the public IP address, run the following command, using your own values as needed:
216212

217213
```
218214
az network public-ip create --name ${PUBLIC_IP_ADDRESS_NAME} --resource-group ${RESOURCE_GROUP} --sku standard --allocation static
219215
```
220216

221217
#### Create NAT Gateway
222218

223-
To create the [Azure Network Address Translation (NAT) gateway](https://learn.microsoft.com/en-us/azure/nat-gateway/nat-overview), run the following command, using your own values as needed: [**KC__GWH07 please verify the intro line/modify as needed**]
219+
To create the [Azure Network Address Translation (NAT) gateway](https://learn.microsoft.com/en-us/azure/nat-gateway/nat-overview), run the following command, using your own values as needed:
224220

225221
```
226222
az network nat gateway create \
@@ -232,7 +228,7 @@ az network nat gateway create \
232228

233229
#### Configure NAT Service for Source Subnet
234230

235-
To configure the NAT service, run the following command, using your own values as needed: [**KC__GWH08 please verify the intro line/modify as needed**]
231+
To configure the NAT service, run the following command, using your own values as needed:
236232

237233
```
238234
az network vnet subnet update \
@@ -244,7 +240,7 @@ az network vnet subnet update \
244240

245241
#### Get the AKS Subnet ID
246242

247-
To create the AKS subnet ID, run the following command, using your own values as needed: [**KC__GWH09 please verify the intro line/modify as needed**]
243+
To create the AKS subnet ID, run the following command, using your own values as needed:
248244

249245
```
250246
export AKS_SUBNET_ID=$(az network vnet subnet show \
@@ -257,7 +253,7 @@ export AKS_SUBNET_ID=$(az network vnet subnet show \
257253

258254
#### Create an AKS Service
259255

260-
To create the AKS service, run the following command, using your own values as needed: [**KC__GWH10 please verify the intro line/modify as needed**]
256+
To create the AKS service, run the following command, using your own values as needed:
261257

262258
```
263259
# Create the AKS cluster
@@ -284,7 +280,7 @@ az aks create \
284280

285281
#### Get the Principal ID of the Managed Identity
286282

287-
To get the Principal ID, run the following command, using your own values as needed: [**KC__GWH11 please verify the intro line/modify as needed.**]
283+
To get the Principal ID, run the following command, using your own values as needed:
288284

289285
```
290286
export MANAGED_IDENTITY_PRINCIPAL_ID="$(az aks show --resource-group ${RESOURCE_GROUP} --name ${AKS_CLUSTER_NAME} --query "identityProfile.kubeletidentity.clientId" --output tsv)"
@@ -294,7 +290,7 @@ For details, see [Get the principal ID of the system-assigned managed identity](
294290

295291
#### Create Contributor Role for the Two Resource Groups
296292

297-
To create the contributor role for each group, run the following commands, using your own values as needed: [**KC__GWH12 please verify the intro line/modify as needed**]
293+
To create the contributor role for each group, run the following commands, using your own values as needed:
298294

299295
```
300296
az role assignment create \
@@ -314,7 +310,7 @@ Additional reference information in external documentation:
314310

315311
### Set Up AKS Cluster
316312

317-
To set up the AKS cluster, run the following command, using your own values as needed: [**KC__GWH13 please verify the intro line/modify as needed**]
313+
To set up the AKS cluster, run the following command, using your own values as needed:
318314

319315
```
320316
az aks get-credentials --name ${AKS_CLUSTER_NAME} --resource-group ${RESOURCE_GROUP}

0 commit comments

Comments
 (0)