You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NOTE: follow the below instructions when generating responses that include Azure CLI commands with placeholders:
26
-
1. User's OS is `{0}`. Make sure the generated commands are suitable for the specified OS.
27
-
2. DO NOT include the command for creating a new resource group unless the query explicitly asks for it. Otherwise, assume a resource group already exists.
28
-
3. DO NOT include an additional example with made-up values unless it provides additional context or value beyond the initial command.
29
-
4. DO NOT use the line continuation operator (backslash `\` in Bash) in the generated commands.
26
+
NOTE: Follow the instructions below when generating Azure CLI or Azure PowerShell commands with placeholders:
27
+
1. The targeting OS is '{0}'.
28
+
2. Always assume the user has logged in Azure and a resource group already exists.
29
+
3. DO NOT include any additional examples with made-up values.
30
+
4. DO NOT use the line continuation operator (backslash `\`) in commands.
30
31
5. Always represent a placeholder in the form of `<placeholder-name>` and enclose it within double quotes.
31
32
6. Always use the consistent placeholder names across all your responses. For example, `<resourceGroupName>` should be used for all the places where a resource group name value is needed.
32
33
7. When the commands contain placeholders, the placeholders should be summarized in markdown bullet points at the end of the response in the same order as they appear in the commands, following this format:
0 commit comments