Azure / Azure/azure-quickstart-templates

Where is a REAL sample of how to pass the secret/values into the 201-key-vault-secret-create template?

Open
#6,767 7 comments 0 reactions 0 assignees View on GitHub
Dominant language
Bicep
Stars
14.9k
Forks
16.2k
Avg merge
6d 21h
Merged PRs (30d)
6

Description

[201-key-vault-secret-create](https://github.com/Azure/azure-quickstart-templates/tree/master/201-key-vault-secret-create)

### Issue Details
The help indicates that the format for the secret key/value pairs is
**Specifies all secrets {\"secretName\":\"\",\"secretValue\":\"\"} wrapped in a secure object.**

I have tried this value directly and get:
```Deployment template validation failed: 'Template parameter JToken type is not valid. Expected 'Object'. Actual 'String'. Please see https://aka.ms/resource-manager-parameter-files for usage details.'. (Code: InvalidTemplate)```

I also tried: {"secretName":"testme","secretValue":"now"}

and got:
```Deployment template validation failed: 'The template resource '[concat(parameters('keyVaultName'), '/', parameters('secretsObject').secrets[copyIndex()].secretName)]' at line '137' and column '5' is not valid: The language expression property 'secrets' doesn't exist, available properties are 'secretName, secretValue'.. Please see https://aka.ms/arm-template-expressions for usage details.'. (Code: InvalidTemplate)```

What is a good example of sending in multiple sets of key/value pairs for secret/values and can you please update the documentation so one doesn't hunt all over Google and Stackoverflow trying to find examples?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the linked 201-key-vault-secret-create template and its help or parameter definition, then compare the documented secretsObject shape with the deployment errors and any examples in the template directory. Done means the template documentation includes a working example showing multiple secret name/value pairs and the expected input structure.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.