Skip to content

Commit 27d3984

Browse files
authored
Merge pull request #288909 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents b7dcf22 + 2047261 commit 27d3984

File tree

6 files changed

+24
-9
lines changed

6 files changed

+24
-9
lines changed

articles/azure-functions/durable/quickstart-mssql.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -91,6 +91,14 @@ docker exec -d mssql-server /opt/mssql-tools/bin/sqlcmd -S . -U sa -P "$pw" -Q "
9191

9292
After you run these commands, you should have a local SQL Server running on Docker and listening on port 1443. If port 1443 conflicts with another service, you can rerun these commands after you change the variable `$port` to a different value.
9393

94+
If you receive this error when running the last command:
95+
96+
```
97+
Error response from daemon: OCI runtime exec failed: exec failed: unable to start container process: exec: "/opt/mssql-tools/bin/sqlcmd": stat /opt/mssql-tools/bin/sqlcmd: no such file or directory: unknown
98+
```
99+
100+
It's likely that the folder `/opt/mssql-tools/bin/sqlcmd` does not exist. Open Docker Desktop, select your SQL Server Docker container, select Files and browse for the mssql-tools folder. This folder might have a different name, such as `/opt/mssql-tools18/bin/sqlcmd`. Update the last line of code accordingly and run it gain.
101+
94102
> [!NOTE]
95103
> To stop and delete a running container, you can use `docker stop <containerName>` and `docker rm <containerName>` respectively. You can use these commands to re-create your container and to stop the container when you finish this quickstart. For more assistance, run `docker --help`.
96104

articles/azure-resource-manager/bicep/bicep-functions-array.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -158,19 +158,19 @@ The output from the preceding example with the default values is:
158158

159159
`empty(itemToTest)`
160160

161-
Determines if an array, object, or string is empty.
161+
Determines if an array, object, or string is empty or null.
162162

163163
Namespace: [sys](bicep-functions.md#namespaces-for-functions).
164164

165165
### Parameters
166166

167167
| Parameter | Required | Type | Description |
168168
|:--- |:--- |:--- |:--- |
169-
| itemToTest |Yes |array, object, or string |The value to check if it's empty. |
169+
| itemToTest |Yes |array, object, or string |The value to check if it's empty or null. |
170170

171171
### Return value
172172

173-
Returns **True** if the value is empty; otherwise, **False**.
173+
Returns **True** if the value is empty or null; otherwise, **False**.
174174

175175
### Example
176176

@@ -180,10 +180,12 @@ The following example checks whether an array, object, and string are empty.
180180
param testArray array = []
181181
param testObject object = {}
182182
param testString string = ''
183+
param testNullString string?
183184
184185
output arrayEmpty bool = empty(testArray)
185186
output objectEmpty bool = empty(testObject)
186187
output stringEmpty bool = empty(testString)
188+
output stringNull bool = empty(testNullString)
187189
```
188190

189191
The output from the preceding example with the default values is:
@@ -193,6 +195,7 @@ The output from the preceding example with the default values is:
193195
| arrayEmpty | Bool | True |
194196
| objectEmpty | Bool | True |
195197
| stringEmpty | Bool | True |
198+
| stringNull | Bool | True |
196199

197200
### Quickstart examples
198201

articles/azure-resource-manager/bicep/bicep-functions-string.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -331,19 +331,19 @@ The output from the preceding example with the default values is:
331331

332332
`empty(itemToTest)`
333333

334-
Determines if an array, object, or string is empty.
334+
Determines if an array, object, or string is empty or null.
335335

336336
Namespace: [sys](bicep-functions.md#namespaces-for-functions).
337337

338338
### Parameters
339339

340340
| Parameter | Required | Type | Description |
341341
|:--- |:--- |:--- |:--- |
342-
| itemToTest |Yes |array, object, or string |The value to check if it's empty. |
342+
| itemToTest |Yes |array, object, or string |The value to check if it's empty or null. |
343343

344344
### Return value
345345

346-
Returns `True` if the value is empty; otherwise, `False`.
346+
Returns **True** if the value is empty or null; otherwise, **False**.
347347

348348
### Examples
349349

@@ -353,10 +353,12 @@ The following example checks whether an array, object, and string are empty.
353353
param testArray array = []
354354
param testObject object = {}
355355
param testString string = ''
356+
param testNullString string?
356357
357358
output arrayEmpty bool = empty(testArray)
358359
output objectEmpty bool = empty(testObject)
359360
output stringEmpty bool = empty(testString)
361+
output stringNull bool = empty(testNullString)
360362
```
361363

362364
The output from the preceding example with the default values is:
@@ -366,6 +368,7 @@ The output from the preceding example with the default values is:
366368
| arrayEmpty | Bool | True |
367369
| objectEmpty | Bool | True |
368370
| stringEmpty | Bool | True |
371+
| stringNull | Bool | True |
369372

370373
## endsWith
371374

articles/azure-vmware/azure-vmware-solution-known-issues.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,7 @@ Refer to the table to find details about resolution dates or possible workaround
1515

1616
|Issue | Date discovered | Workaround | Date resolved |
1717
| :------------------------------------- | :------------ | :------------- | :------------- |
18+
| [VMSA-2024-0021](https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/25019) VMware HCX addresses an authenticated SQL injection vulnerability (CVE-2024-38814) | 2024 | None | October 2024- Resolved in [HCX 4.10.1](https://docs.vmware.com/en/VMware-HCX/4.10.1/rn/vmware-hcx-4101-release-notes/index.html#What's%20New), [HCX 4.9.2](https://docs.vmware.com/en/VMware-HCX/4.9.2/rn/vmware-hcx-492-release-notes/index.html#What's%20New) and [HCX 4.8.3](https://docs.vmware.com/en/VMware-HCX/4.8.3/rn/vmware-hcx-483-release-notes/index.html#What's%20New)
1819
| [VMSA-2021-002 ESXiArgs](https://www.vmware.com/security/advisories/VMSA-2021-0002.html) OpenSLP vulnerability publicized in February 2023 | 2021 | [Disable OpenSLP service](https://kb.vmware.com/s/article/76372) | February 2021 - Resolved in [ESXi 7.0 U3c](architecture-private-clouds.md#vmware-software-versions) |
1920
| After my private cloud NSX-T Data Center upgrade to version [3.2.2](https://docs.vmware.com/en/VMware-NSX/3.2.2/rn/vmware-nsxt-data-center-322-release-notes/index.html), the NSX-T Manager **DNS - Forwarder Upstream Server Timeout** alarm is raised | February 2023 | [Enable private cloud internet Access](architecture-design-public-internet-access.md), alarm is raised because NSX-T Manager can't access the configured CloudFlare DNS server. Otherwise, [change the default DNS zone to point to a valid and reachable DNS server.](configure-dns-azure-vmware-solution.md) | February 2023 |
2021
| When first logging in to the vSphere Client, the **Cluster-n: vSAN health alarms are suppressed** alert is active in the vSphere Client | 2021 | The alert should be considered an informational message, since Microsoft manages the service. Select the **Reset to Green** link to clear it. | 2021 |

articles/container-apps/cors.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ As you enable CORS, you can configure the following settings:
2828
| Allowed origins | List of the origins allowed for cross-origin requests (for example, `https://www.contoso.com`). Controls the [`Access-Control-Allow-Origin`](https://developer.mozilla.org/docs/Web/HTTP/Headers/Access-Control-Allow-Origin) response header. Use `*` to allow all. |
2929
| Allowed methods | List of HTTP request methods allowed in cross-origin requests. Controls the [`Access-Control-Allow-Methods`](https://developer.mozilla.org/docs/Web/HTTP/Headers/Access-Control-Allow-Methods) response header. Use `*` to allow all. |
3030
| Allowed headers | List of the headers allowed in cross-origin requests. Controls the [`Access-Control-Allow-Headers`](https://developer.mozilla.org/docs/Web/HTTP/Headers/Access-Control-Allow-Headers) response header. Use `*` to allow all. |
31-
| Expose headers | By default, not all response headers are exposed to client-side JavaScript code in a cross-origin request. Exposed headers are extra headers servers can include in a response. Controls the [`Access-Control-Expose-Headers`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Expose-Headers) response header. Use `*` to expose all. |
31+
| Expose headers | By default, not all response headers are exposed to client-side JavaScript code in a cross-origin request. Exposed headers are extra headers servers can include in a response. Controls the [`Access-Control-Expose-Headers`](https://developer.mozilla.org/docs/Web/HTTP/Headers/Access-Control-Expose-Headers) response header. Use `*` to expose all. |
3232

3333
::: zone-end
3434

articles/container-apps/user-defined-routes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,14 +2,14 @@
22
title: Container Apps outbound traffic control with Azure Firewall
33
description: Use Azure Firewall to route outbound traffic from Container Apps to the internet, private IP addresses, and Azure services.
44
services: container-apps
5-
author: cachai
5+
author: cachai2
66
ms.service: azure-container-apps
77
ms.author: cachai
88
ms.topic: article
99
ms.date: 08/29/2023
1010
---
1111

12-
# Control outbound traffic with user defined routes
12+
# Control outbound traffic in Azure Container Apps with user defined routes
1313

1414
> [!NOTE]
1515
> This feature is only supported for the workload profiles environment type.

0 commit comments

Comments
 (0)