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

azd down does not purge cognitive service #1941

Closed
jenny0322 opened this issue Apr 13, 2023 · 3 comments · Fixed by #2257
Closed

azd down does not purge cognitive service #1941

jenny0322 opened this issue Apr 13, 2023 · 3 comments · Fixed by #2257
Assignees
Labels
customer-reported identify a customer issue question

Comments

@jenny0322
Copy link

When the command "azd down" is ran, cognitive service does not get purged so "azd provision" is re-run after "azd down", deployment would fail
A clear and concise description of what the bug is.

Expected behavior
User is asked whether he/she would like to purge cognitive service (similar to API Management) when the user runs "azd down"

@vhvb1989 vhvb1989 transferred this issue from Azure/awesome-azd Apr 13, 2023
@ghost ghost added needs-triage For new issues customer-reported identify a customer issue question labels Apr 13, 2023
@rajeshkamal5050
Copy link

@hemarina do we handle purging cognitive service?

@ellismg @weikanglim @vhvb1989 @wbreza the deletion and purging of resources is part of azd core? given that provisioning is handled via IaC shouldn't the deletion/purging be handled via IaC instead of handled in core? Can't we make this as a template ones?

@vhvb1989
Copy link
Member

vhvb1989 commented May 9, 2023

openAI has some issues while deleting it. It requires some extra steps. That's why azd is not covering this.
@jongio can you share the process for deleting it ?

@hemarina
Copy link
Contributor

hemarina commented May 9, 2023

We don't have support for purging cognitive service. Got the steps from Jon and Arun. Will take a look and work on this as next issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported identify a customer issue question
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants