Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Suggestion] It would be better to remove the containerized function app when executing containerized function app unsupported commands #4174

Open
v-ruizh opened this issue Jun 11, 2024 · 2 comments
Labels
AT-CTI Created by CTI team

Comments

@v-ruizh
Copy link

v-ruizh commented Jun 11, 2024

OS: All
Build Version: v1.15.1-alpha.0
Regression: Not a Regression

Repro Steps:

  1. Create a containerized function app.
  2. F1 -> Select "Azure Functions: Configure Deployment Source...".
  3. Check whether containerized function app shows in the function app list.

Actual:
The containerized function app shows in the function app list.
image

Suggestion:
It would be better to remove the containerized function app when executing containerized function app unsupported commands.

More Info:

  1. Fail to execute "Configure Deployment Source..." command for a containerized function app.
    image
  2. This bug also reproduces when executing other containerized function app unsupported commands, such as "Start/Stop Streaming Logs", "Start/Restart/Stop", "Deploy to Slot"...
@v-ruizh v-ruizh added the AT-CTI Created by CTI team label Jun 11, 2024
@motm32
Copy link
Contributor

motm32 commented Jun 11, 2024

Hello! Thanks for filing this issue. Even though the containerized function app does show in the quick pick when a containerized function app is chosen for these unsupported commands an error like this should show up:
image
Please let me know if that is not the case!

@v-ruizh
Copy link
Author

v-ruizh commented Jun 12, 2024

Yes, I added the more info in the bug. There is an error when executing the unsupported commands for containerized function app. I saw you have fixed the same issue for Deploy commands, so log a new bug for other commands.

Is this by design for other unsupported commands?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AT-CTI Created by CTI team
Projects
None yet
Development

No branches or pull requests

2 participants