microsoft / microsoft/vscode-azurecontainerapps

Azure Activity Log does not show secret creation/selection when adding Azure Queue scale rules

Open
#1,124 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

AT-CTI
Dominant language
TypeScript
Stars
42
Forks
21
Avg merge
3d 7h
Merged PRs (30d)
2

Description

OS: Win 11 x64
Build Version: 20260626.1
Regression: Not a Regression

Repro Steps:

  1. Execute "Add Scale Rule..." command.
  2. Select "Azure queue" as the scale type.
  3. During setup, either: create a new secret or select an existing secret.
  4. Complete the wizard and deploy the changes.
  5. Compare the information shown in:
  • Azure Activity Log
  • Output Window

Expect:
The Azure Activity Log should include all user-facing configuration steps involved in creating the Azure Queue scale rule, including secret creation or secret selection.

Actual:
The Azure Activity Log only shows entries similar to:
Image
However, the Output Window contains additional information, such as:
Image
The secret-related operation is not reflected in the Azure Activity Log.

More Info:
When configuring an Azure Queue scale rule, users are required to either create a new secret or select an existing one. This is a user-visible configuration step rather than an internal implementation detail. Omitting this information from the Activity Log makes it difficult to understand what changes were applied and reduces the completeness of the operation history.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the “Add Scale Rule...” command for the Azure queue flow, focusing on where secret creation or selection is recorded for the Azure Activity Log. Compare the Activity Log entries with the Output Window for both secret paths; done means the user-facing secret operation appears in the Activity Log after deployment.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, typescript, vscode
Domain
cloud, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.