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
Update flight flags and make corresponding changes (#355)
1. Add the flag `pipelineorchestration` per the Azure Copilot team's request.
2. Update flag values based on the values used by Azure Portal, and remove 2 flags that are no longer used by Azure Portal.
3. Update the topic names for AzCLI handler and AzPS handler. They changed after adopting the new flag values.
4. Simplify the instruction prompt to save words for the input. Also include Azure PowerShell in the instruction.
5. Use better OS description for the instruction prompt.
6. Log the topic name for every response, for diagnostic purpose. We already send this information in telemetry.
7. Fix a bug in response parsing in the validation of the beginning of placeholder section.
8. Fix the status report to only report `ProgressTopic` status, which are progress reports only (fix#352).
9. Special case `TaskCanceledException` in AzCLI metadata query for logging and telemetry collection. This exception simply means the query action timed out after 1200 ms. Given that the metadata endpoint is an Azure Function, this could easily happen when the query hits a cold start of the function app. So, we don't want to log the exception object here.
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