Merge pull request #78621 from zr-msft/ds-secrets-yaml

[Dev Spaces] added callout for using secrets

Author: PRMerger14

articles/dev-spaces/how-to/manage-secrets.md

@@ -14,8 +14,8 @@ keywords: "Docker, Kubernetes, Azure, AKS, Azure Container Service, containers"
 
 Your services might require certain passwords, connection strings, and other secrets, such as for databases or other secure Azure services. By setting the values of these secrets in configuration files, you can make them available in your code as environment variables.  These must be handled with care to avoid compromising the security of the secrets.
 
-Azure Dev Spaces provides two recommended options for storing secrets: in the values.dev.yaml file, and inline directly in azds.yaml. It's not recommended to store secrets in values.yaml.
- 
+Azure Dev Spaces provides two recommended, streamlined options for storing secrets in Helm charts generated by the Azure Dev Spaces client tooling: in the values.dev.yaml file, and inline directly in azds.yaml. It's not recommended to store secrets in values.yaml. Outside of the two approaches for Helm charts generated by the client tooling defined in this article, if you create your own Helm chart, you can use the Helm chart directly to manage and store secrets.
+
 ## Method 1: values.dev.yaml
 1. Open VS Code with your project that is enabled for Azure Dev Spaces.
 2. Add a file named _values.dev.yaml_ in the same folder as existing _azds.yaml_ and define your secret key and values, as in the following example: