Skip to content

Commit 40f46be

Browse files
committed
update
1 parent fa33e96 commit 40f46be

File tree

2 files changed

+1
-3
lines changed

2 files changed

+1
-3
lines changed

articles/azure-resource-manager/bicep/data-types.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Data types in Bicep
33
description: This article describes the data types that are available in Bicep.
44
ms.topic: reference
5-
ms.date: 01/10/2025
5+
ms.date: 05/09/2025
66
ms.custom: devx-track-bicep
77
---
88

articles/azure-resource-manager/bicep/outputs.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -163,8 +163,6 @@ output demoPassword string
163163
output demoSecretObject object
164164
```
165165

166-
There are several linter rules related to this decorator: [Secure parameter default](./linter-rule-secure-parameter-default.md), [Secure parameters in nested deployments](./linter-rule-secure-params-in-nested-deploy.md), [Secure secrets in parameters](./linter-rule-secure-secrets-in-parameters.md).
167-
168166
The `@secure()` decorator is valid only for outputs of type string or object, as these align with the [secureString](../templates/syntax.md#outputs) and [secureObject](../templates/syntax.md#outputs) types in ARM templates. To pass arrays or numbers securely, wrap them in a secureObject or serialize them as a secureString.
169167

170168
## Conditional output

0 commit comments

Comments
 (0)