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

Azure Resource names not matching Azure Resource and unwanted/unused resource are created. #493

Closed
nkidambi opened this issue Feb 8, 2024 · 2 comments · Fixed by #675
Closed
Labels
enhancement New feature or request
Milestone

Comments

@nkidambi
Copy link
Collaborator

nkidambi commented Feb 8, 2024

Bug Details

Deployment Branch: Main
** Bug 1: Names of App Settings and Azure Resources don't match
After deploying the main branch, the app settings for Azure Functions and the secret key in Azure Key Vault is referencing to Form Recognizer for a Document Intelligence Resource. Also the name of the Document Intelligence Resource has "fr" in its name. This is causing some confusion because when the customer is searching for resources, they now have to use FR instead of document intelligence.

This is causing confusion for my customer.

** Bug 2: Unused resources created
Media Service and Azure AI Video Indexer are being created despite it not being used. This is confusing and raising questions related to cost.

What is the expected behavior?
For Bug 1: The name to reflect the type of the resource created

For Bug 2: Not deploy/create unused/unwanted azure resources

Screenshots
IA Bugs

@dayland dayland added the enhancement New feature or request label Feb 8, 2024
@dayland dayland added this to the 1.1 milestone Feb 8, 2024
@georearl
Copy link
Contributor

video indexer & media services is no longer created

@dayland
Copy link
Contributor

dayland commented Apr 29, 2024

Resolved with latest release v1.1

@dayland dayland closed this as completed Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants