Jon Gallant
Jon Gallant
@puicchan to comment as that is the same error message she originally posted.
They could specify the group name or modify the bicep template to use 'existing' (bicep keyword). In main.bicep ``` resource resourceGroup 'Microsoft.Resources/resourceGroups@2020-06-01' = { name: '${name}rg' location: location } ```...
Let's consider how we can build this switch from sub to rg deployments with iac only. We need to be very careful about mixing declarative and imperative operations as we...
Interesting, we could inspect the bicep entry point, determine the scope and then make a decision there so it is flexible.
@colbylwilliams and @danieljurek Today, azd doesn't support the resourceGroup scope, but in the mean-time, can you see if this will work for you? Have a look at the commit here:...
I continue to see this issue as well. In the func test, we call infra/create and then immediately call deploy and sometimes the func isn't fully ready to accept code.
We'll want to ship both azdo and gh workflow files in our templates. So they are in the clear. We definitely don't want to create a new template just for...
Triage: Not a blocker, but Matt thinks he can do this for public preview.
@ellismg - If you don't filter by RG you'll get resources that have the same azd-service-name tag in two diff rgs and results can be unpredictable.
I believe this is related to us using the environment name as the deployment name. We may need to randomize the deployment name or include the location in the name.