microsoft / microsoft/vscode-azurecontainerapps

[Suggestion] It would be better to add revisions in the list when executing "Azure Container Apps: Activate Revision/Deactivate Revision/Restart Revision" command from command palette

Open
#189 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

OS: All
Build Version: 20220908.8

Repro Steps:

  1. Right click a container app -> Click "Choose Revision Model..." -> Select "Multiple".
  2. F1 -> Azure Container Apps: Activate Revision -> Select a subscription -> Select a container app environment -> Select the above container app.
  3. Check whether the revisions show in the list.

Actual:

  1. The revisions don't show in the list.
  2. Execute command "Azure Container Apps: Activate Revision" directly.

Suggestion:
It would be better to add revisions in the list when executing "Azure Container Apps: Activate Revision/Deactivate Revision/Restart Revision" command from command palette, like below:
Screen Shot 2022-09-09 at 18 08 34

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 reproducing the issue through the Azure Container Apps: Activate Revision, Deactivate Revision, and Restart Revision commands from the command palette after selecting Multiple revision mode. Trace the command flow after selecting the subscription, environment, and container app. Done means the available revisions appear in the list and each command can be executed against a selected revision.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, typescript, vscode
Domain
cloud, developer-experience
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.