Work item related to the monorepo work: #607
What to do:
-
Remove the auto-naming of resources based on the workspace name. All apps in the monorepo will share the same root workspace, so this no longer makes as much sense. We can still try to suggest and pre-fill a name for the user on prompt, but the best method for this is still up for debate.
-
Ensure naming logic works for different combinations of existing resource names. I think this mostly already works, but I wanted to put in a note here to double check and improve as necessary. As a reminder, when we go to validate existing resources, we could find any of the listed resources (resource group, container app, container registry, etc.) no longer existing. We will have to create and name new resources for any that are missing.
Work item related to the monorepo work: #607
What to do:
Remove the auto-naming of resources based on the workspace name. All apps in the monorepo will share the same root workspace, so this no longer makes as much sense. We can still try to suggest and pre-fill a name for the user on prompt, but the best method for this is still up for debate.
Ensure naming logic works for different combinations of existing resource names. I think this mostly already works, but I wanted to put in a note here to double check and improve as necessary. As a reminder, when we go to validate existing resources, we could find any of the listed resources (resource group, container app, container registry, etc.) no longer existing. We will have to create and name new resources for any that are missing.
Being able to smartly detect and use resource validate inputs would be nice, but may be a bit of a stretch goal for this first pass.
See this for more info: Refactor
DefaultResourcesNameStepto utilize each resource step'svalidateInput#603