Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [X ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

1. Clone the repo to a Windows machine where git is configured globally to core.autocrlf true.
2. Open the project in VS Code and allow it to restart in a Remote Container environment.
3. You'll get an error related to the docker-in-docker-debian.sh file (CRLF error on Line 11, 18, etc.).
4. Process fails as a result of the above error.

Any log messages given by the failure

Invalid command in docker-in-docker-debian.sh (unrecognized command is the result of \r endings)

Expected/desired behavior

Start up the Remote Container environment.

OS and Version?

Windows 10 21H2 (OS Build 19044.1889) - I'm on a virtual machine provided to me for use in another scenario

Versions

VS Code 1.70.2

Mention any other details that might be useful

It looks like this is an issue with how git is configured on this particular Windows machine. I did the following to fix the issue:

• Ran git config --global core.autocrlf false
• Recloned the project and allowed VS Code to run the Remote Container environment.

It might be helpful to mention this in the build-and-run.md file for others who may hit the issue on Windows. Another option to help make it automatic would be to add a .gitattributes file with * text=auto eol=lf in it (although I'd have to validate that in this case).

This issue is for a:

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Mention any other details that might be useful

Regarding this quote in the README:

IMPORTANT: In general, each microservice should have an independent release and deployment. For the sake of this sample we are building and deploying as part of a single repo

Will this info/walkthrough be available soon?

Thanks

I am using Azure Container apps with Azure Blob Store as a state store. It is a simple Hello World (weather service) app using dotnet 6. App starts up fine, on Post I am trying to save the generated weather information to Azure Blob Store as JSON. I have configured Dapr components in Azure Container Apps for StateStore using Azure blob storage. I am using storage key (secondary key) as explained in this Microsoft documentation

Upon doing a Swagger and looking at log I get the following error.

Dapr.DaprException: State operation failed: the Dapr endpoint indicated a failure. See InnerException for details. 2022-07-17T01:10:35.716245402Z ---> Grpc.Core.RpcException: Status(StatusCode="Internal", Detail="failed saving state in state store statestore: -> github.com/Azure/azure-storage-blob-go/azblob.newStorageError, /home/vsts/work/1/go/pkg/mod/github.com/!azure/[email protected]/azblob/zc_storage_error.go:42 2022-07-17T01:10:35.716524109Z ===== RESPONSE ERROR (ServiceCode=AuthenticationFailed) ===== 2022-07-17T01:10:35.716795515Z Description=Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature. 2022-07-17T01:10:35.716812515Z RequestId:863bcef4-401e-0069-5f7a-99724b000000 2022-07-17T01:10:35.716820115Z Time:2022-07-17T01:10:35.7137648Z, Details: 2022-07-17T01:10:35.716825516Z AuthenticationErrorDetail: Issuer validation failed. Issuer did not match. 2022-07-17T01:10:35.716831516Z Code: AuthenticationFailed

RESPONSE Status: 403 Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.

I am unsure what I am missing since I am not making any additional config in storage account such as VNET service end point etc. Account is enabled for Key access. Any help is appreciated.

Below is the code that I am using

using var client = new DaprClientBuilder().Build();

var forecast = new WeatherForecast()

{
Date = DateTime.Now.AddDays(1),
TemperatureC = Random.Shared.Next(-20, 55),
Summary = Summaries[Random.Shared.Next(Summaries.Length)]
};

await client.SaveStateAsync<WeatherForecast>(stateStoreName,key,forecast);

stateStoreName is "statestore" which is what i have names in Dapr Components in ACS
key is a string "weatherforecast"

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

It seems from the example that APIM would provide no protection to the container apps if the underlying FQDN was known

Please provide us with the following information:

This issue is for a: (mark with an x)

- [X ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

1. Launch the app in VS Code and enable Remote Containers.
2. Run debug All Services.
3. Web page launches and an order can be created and viewed.
4. When trying to view the Inventory status for the order Id (I created an order with an Id of 2) a 500 error occurs.

Any log messages given by the failure

vscode ➜ /workspaces/container-apps-store-api-microservice/node-service $  cd /workspaces/container-apps-store-api-microservice/node-service ; /usr/bin/env DAPR_HTTP_PORT=3501 DAPR_GRPC_PORT=50001 DAPR_METRICS_PORT=9091 INVENTORY_SERVICE_NAME=go-app ORDER_SERVICE_NAME=python-app PORT=3000 'NODE_OPTIONS=--require /vscode/vscode-server/bin/linux-x64/e4503b30fc78200f846c62cf8091b76ff5547662/extensions/ms-vscode.js-debug/src/bootloader.bundle.js --inspect-publish-uid=http' 'VSCODE_INSPECTOR_OPTIONS={"inspectorIpc":"/tmp/node-cdp.689-3.sock","deferredMode":false,"waitForDebugger":"","execPath":"/usr/local/share/nvm/current/bin/node","onlyEntrypoint":false,"autoAttachMode":"always","mandatePortTracking":true,"fileCallback":"/tmp/node-debug-callback-8bab54b1c8fd9f9d"}' /usr/local/share/nvm/current/bin/npm run start 
Debugger attached.

> [email protected] start /workspaces/container-apps-store-api-microservice/node-service
> node ./bin/www

Debugger attached.
listening on port 3000
GET /dapr/config 404 4956.315 ms - 1461
GET / 304 147.368 ms - -
GET /stylesheets/style.css 304 9.754 ms - -
GET /script.js 304 30.656 ms - -
GET /favicon.ico 404 27.534 ms - 1461
Service invoke to: http://localhost:3501/order?id=2
GET /order?id=2 304 264.462 ms - -
(node:11236) UnhandledPromiseRejectionWarning: Error: Request failed with status code 500
    at createError (/workspaces/container-apps-store-api-microservice/node-service/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/workspaces/container-apps-store-api-microservice/node-service/node_modules/axios/lib/core/settle.js:17:12)
    at IncomingMessage.handleStreamEnd (/workspaces/container-apps-store-api-microservice/node-service/node_modules/axios/lib/adapters/http.js:293:11)
    at IncomingMessage.emit (events.js:412:35)
    at endReadableNT (internal/streams/readable.js:1333:12)
    at processTicksAndRejections (internal/process/task_queues.js:82:21)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:11236) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:11236) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Expected/desired behavior

Show inventory status

OS and Version?

Windows 10 21H2 (OS Build 19044.1889) - on a virtual machine provided to me for use in another scenario

Versions

VS Code 1.70.2

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [X ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Deploy any container in Azure Container App Environment

Any log messages given by the failure

No
I am not able to monitor the container logs. Will we be getting rich telemetry on my hosted container as we get for any PaaS platform? Like Kudu in WebApp where we get a console of instance hosting a webApp.

Expected/desired behavior

More Enriched Logs and Insights and Logs.

OS and Version?

Linux/Windows

Versions

Mention any other details that might be useful

My Team is looking to move away from hosting and managing the Kubernetes cluster and wants to try Azure Container Apps. As we hosted our first container as POC on Container App, we are not able to get insights on the container logs which we can easily access in AKS. Please suggest
Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Mention any other details that might be useful

One really nice feature of container apps is using multiple revisions and Blue Green Deployments.

I tried to structure a deployment workflow around bicep templates like in this sample repo, but I was unable to get revisions to work correctly. Is this just something that will only be supported by using iterative deployments or will this be possible using the bicep deployment workflow as well?

Documentation or an example for this would be greatly appreciated!

Thanks in advance.

This issue is for a: (mark with an x)

- [ x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

1. Create azure container registry in bicep
2. Create KV
3. Create container app environment
4. Store password for ACR in KV
5. Build and push docker image to private ACR
6. Deploy azure container app with new image (via bicep)

Any log messages given by the failure

ERROR: ***"status":"Failed","error":***"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[***"code":"Conflict","message":"***\r\n  \"status\": \"Failed\",\r\n  \"error\": ***\r\n    \"code\": \"ResourceDeploymentFailure\",\r\n    \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n    \"details\": [\r\n      ***\r\n        \"code\": \"DeploymentFailed\",\r\n        \"message\": \"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.\",\r\n        \"details\": [\r\n          ***\r\n            \"code\": \"BadRequest\",\r\n            \"message\": \"***\\r\\n  \\\"code\\\": \\\"WebhookInvalidParameterValue\\\",\\r\\n  \\\"message\\\": \\\"The following field(s) are either invalid or missing. Invalid value: \\\\\\\"cosmossdkidentitydemoacr.azurecr.io/books-api:7826629ba32ba4f08d1e7255dc24849fe9018bc6\\\\\\\": GET https:?scope=repository%3Abooks-api%3Apull&service=cosmossdkidentitydemoacr.azurecr.io: UNAUTHORIZED: authentication required, visit https://aka.ms/acr/authorization for more information.: template.containers.books-api.image.\\\"\\r\\n***\"\r\n          ***\r\n        ]\r\n      ***\r\n    ]\r\n  ***\r\n***"***]***
[22](https://github.com/mumby0168/cosmos-repository-sdk-identity/runs/6627441780?check_suite_focus=true#step:5:23)
Error: Error: az cli script failed.

Expected/desired behavior

The image is pulled and the application deploys

OS and Version?

Via Github Actions linux.

Versions

Mention any other details that might be useful

I have all the bicep defined in this repository: https://github.com/mumby0168/cosmos-repository-sdk-identity/tree/deploy

The error is also present in this github actions run:

https://github.com/mumby0168/cosmos-repository-sdk-identity/actions/runs/2397180530

Is this the correct way to deploy to azure container apps? I did not want to use containerapp up as then my bicep is not repeatable.

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Open repo in VS Code Spaces
Alternatively, docker build the dockerfile in the /.devcontainer folder

Any log messages given by the failure

=> ERROR [11/11] RUN sed -i 's/statestore/orders/g' ${HOME}/.dapr/components/statestore.yaml       0.5s
------
 > [11/11] RUN sed -i 's/statestore/orders/g' ${HOME}/.dapr/components/statestore.yaml:
#15 0.463 sed: can't read /root/.dapr/components/statestore.yaml: No such file or directory
------
executor failed running [/bin/sh -c sed -i 's/statestore/orders/g' ${HOME}/.dapr/components/statestore.yaml]: exit code: 2
The terminal process "bash '-c', 'docker build --pull --rm -f ".devcontainer/Dockerfile" -t containerappsstoreapimicroservice:latest ".devcontainer"'" terminated with exit code: 1.

Expected/desired behavior

No error

Mention any other details that might be usefull

likely a minor path issue for statestore. I can do shortly.

This issue is for a: (mark with an x)

- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

1. Follow toturial: https://learn.microsoft.com/en-us/azure/container-apps/dapr-github-actions?tabs=bash
2. Github actions run well
3. Access application url of node-service: https://node-app.wonderfulrock-6c248728.canadacentral.azurecontainerapps.io/
4. Input id and item, then create new order
5. See error message

Any log messages given by the failure

"<_InactiveRpcError of RPC that terminated with:\n\tstatus = StatusCode.FAILED_PRECONDITION\n\tdetails = "state store is not configured"\n\tdebug_error_string = "UNKNOWN:Error received from peer ipv4:127.0.0.1:50001 {created_time:"2022-10-10T17:04:06.002386593+00:00", grpc_status:9, grpc_message:"state store is not configured"}"\n>"

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Command line on MacOS, all other procedures are done on Azure Portal

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

Any log messages given by the failure

"<_InactiveRpcError of RPC that terminated with:\n\tstatus = StatusCode.FAILED_PRECONDITION\n\tdetails = "state store is not configured"\n\tdebug_error_string = "UNKNOWN:Error received from peer ipv4:127.0.0.1:50001 {created_time:"2022-10-10T17:04:06.002386593+00:00", grpc_status:9, grpc_message:"state store is not configured"}"\n>"

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Command line on MacOS, all other procedures are done on Azure Portal

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

Was the components directory left out of this repo intentionally? It's required to run locally.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [X ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

• Follow the steps at https://learn.microsoft.com/en-us/azure/container-apps/dapr-github-actions?tabs=bash
• GitHub action should deploy everything successfully (successfully from a GitHub standpoint)
• node-app container app will provision initially but then fail due to error below

Any log messages given by the failure

• Failed to pull image "ghcr.io/danwahlin/container-apps-store-api-microservice/node-service:sha-ac6a0a4": rpc error: code = Unknown desc = failed to pull and unpack image "ghcr.io/danwahlin/container-apps-store-api-microservice/node-service:sha-ac6a0a4": failed to resolve reference "ghcr.io/danwahlin/container-apps-store-api-microservice/node-service:sha-ac6a0a4": failed to authorize: failed to fetch oauth token: unexpected status: 403 Forbidden
• Error: ErrImagePull
• Liveness probe failed: HTTP probe failed with statuscode: 500

Expected/desired behavior

Container App should load the image and then run

OS and Version?

Mac Monterey 12.6

Mention any other details that might be useful

I'm able to run docker pull ghcr.io/danwahlin/container-apps-store-api-microservice/node-service:sha-ac6a0a4 successfully from my local machine. The node-app container app doesn't seem to be able to pull that image though. I see that the container app Image type is Private but the package is public in GitHub.

I changed isPrivateRegistry to true in deploy/main.bicep and it seems to work now. See PR #32.

---

Thanks! We'll be in touch soon.

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

cd deploy
az bicep build --file main.bicep

Any log messages given by the failure

• container-http.bicep(32,23) : Warning BCP081: Resource type "Microsoft.Web/containerApps@2021-03-01" does not have types available.
• environment.bicep(26,16) : Warning BCP036: The property "Flow_Type" expected a value of type "'Bluefield' | null" but the provided value is of type "'Redfield'".
• environment.bicep(27,21) : Warning BCP036: The property "Request_Source" expected a value of type "'rest' | null" but the provided value is of type "'CustomDeployment'".
• environment.bicep(35,5) : Warning BCP037: The property "type" is not allowed on objects of type "KubeEnvironmentProperties". Permissible properties include "aksResourceID", "arcConfiguration", "staticIp". If this is an inaccuracy in the documentation, please report it to the Bicep Team. [https://aka.ms/bicep-type-issues]
• environment.bicep(44,5) : Warning BCP037: The property "containerAppsConfiguration" is not allowed on objects of type "KubeEnvironmentProperties". Permissible properties include "aksResourceID", "arcConfiguration", "staticIp". If this is an inaccuracy in the documentation, please report it to the Bicep Team. [https://aka.ms/bicep-type-issues]

Expected/desired behavior

-There is no documentation for "Microsoft.Web/containerApps".
-"Microsoft.Web/kubeEnvironments" does not mention "type" and "containerAppsConfiguration".
https://docs.microsoft.com/en-us/azure/templates/microsoft.web/kubeenvironments?tabs=bicep

Versions

Bicep CLI version 0.4.1008

Mention any other details that might be useful

Azure/bicep#784 (comment)
Azure/bicep#784 (comment)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x ] documentation issue or request
- [ x] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Unable to see Telemetry in Application Insights.

In my own repo, that's using the workflow and Bicep files provided here (Thank you, life saver) I can't seem to get my services to show in Application Insights.

I'm using Dapr in all my services.

Mention any other details that might be useful

I've made some modifications to the bicep, but all seems okay.

This is just a request to see if it's still working your end :) Just incase API's or something has changed already :)

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Simply fork and clone the solution with the latest VSCode and remote container extension. VSCode recognizes a devcontainer exists and attempts to launch the container as expected. This fails.

Any log messages given by the failure

#0 7.919 /tmp/library-scripts/docker-in-docker-debian.sh: line 30: ` for CURR
'NT_USER in ${POSSIBLE_USERS[@]}; do

ERROR: failed to solve: executor failed running [/bin/sh -c apt-get update &
& apt-get install python3-pip -y && /bin/bash /tmp/library-scripts/docker-in
-docker-debian.sh "${ENABLE_NONROOT_DOCKER}" "${USERNAME}" "${USE_MOBY}" "${DOCK
ER_VERSION}"]: exit code: 2
[14641 ms] Error: Command failed: docker buildx build --load --build-arg BUILDKIT_INLINE_CACHE=1 -f C:\Users\BRENDA~1.CAR\AppData\Local\Temp\devcontainercli\container-features\0.25.2-1671545349879\Dockerfile-with-features -t vsc-container-apps-store-api-microservice-67bbad297964f83c0094e4ae069498d5 --target dev_containers_target_stage --build-arg _DEV_CONTAINERS_BASE_IMAGE=dev_container_auto_added_stage_label c:\temp\container-apps-store-api-microservice.devcontainer
[14641 ms] at Doe (c:\Users\brendan.carroll.vscode\extensions\ms-vscode-remote.remote-containers-0.266.1\dist\spec-node\devContainersSpecCLI.js:1894:1669)
[14641 ms] at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
[14641 ms] at async EF (c:\Users\brendan.carroll.vscode\extensions\ms-vscode-remote.remote-containers-0.266.1\dist\spec-node\devContainersSpecCLI.js:1893:1978)
[14642 ms] at async uT (c:\Users\brendan.carroll.vscode\extensions\ms-vscode-remote.remote-containers-0.266.1\dist\spec-node\devContainersSpecCLI.js:1893:901)
[14642 ms] at async Poe (c:\Users\brendan.carroll.vscode\extensions\ms-vscode-remote.remote-containers-0.266.1\dist\spec-node\devContainersSpecCLI.js:1899:2128)
[14642 ms] at async Zf (c:\Users\brendan.carroll.vscode\extensions\ms-vscode-remote.remote-containers-0.266.1\dist\spec-node\devContainersSpecCLI.js:1899:3278)
[14642 ms] at async aue (c:\Users\brendan.carroll.vscode\extensions\ms-vscode-remote.remote-containers-0.266.1\dist\spec-node\devContainersSpecCLI.js:2020:15276)
[14642 ms] at async oue (c:\Users\brendan.carroll.vscode\extensions\ms-vscode-remote.remote-containers-0.266.1\dist\spec-node\devContainersSpecCLI.js:2020:15030)
[14653 ms] Exit code 1
[14657 ms] Command failed: C:\Users\brendan.carroll\AppData\Local\Programs\Microsoft VS Code\Code.exe --ms-enable-electron-run-as-node c:\Users\brendan.carroll.vscode\extensions\ms-vscode-remote.remote-containers-0.266.1\dist\spec-node\devContainersSpecCLI.js up --user-data-folder c:\Users\brendan.carroll\AppData\Roaming\Code\User\globalStorage\ms-vscode-remote.remote-containers\data --workspace-folder c:\temp\container-apps-store-api-microservice --workspace-mount-consistency cached --id-label devcontainer.local_folder=c:\temp\container-apps-store-api-microservice --log-level debug --log-format json --config c:\temp\container-apps-store-api-microservice.devcontainer\devcontainer.json --default-user-env-probe loginInteractiveShell --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root true
[14657 ms] Exit code 1

Expected/desired behavior

Open as expected

OS and Version?

Windows 10.

Versions

Version: 1.74.1 (user setup)
Commit: 1ad8d514439d5077d2b0b7ee64d2ce82a9308e5a
Date: 2022-12-14T10:30:51.966Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Windows_NT x64 10.0.19044
Sandboxed: No

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [X] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

changing the deployment from canadacentral to useast makes it fail. Is the servie available only in canadacentral for now?
chanezon@8b2bec8

Any log messages given by the failure

ERROR: "status":"Failed","error":"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":["code":"Conflict","message":"\r\n "status": "Failed",\r\n "error": ***\r\n "code": "ResourceDeploymentFailure",\r\n "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n "details": [\r\n ***\r\n "code": "DeploymentFailed",\r\n "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",\r\n "details": [\r\n \r\n "code": "Conflict",\r\n "message": "\r\n \"error\": ***\r\n \"code\": \"MissingSubscriptionRegistration\",\r\n \"message\": \"The subscription is not registered to use namespace 'Microsoft.OperationalInsights'. See https://aka.ms/rps-not-found for how to register subscriptions.\",\r\n \"details\": [\r\n ***\r\n \"code\": \"MissingSubscriptionRegistration\",\r\n \"target\": \"Microsoft.OperationalInsights\",\r\n \"message\": \"The subscription is not registered to use namespace 'Microsoft.OperationalInsights'. See https://aka.ms/rps-not-found for how to register subscriptions.\"\r\n ***\r\n ]\r\n \r\n"\r\n ***,\r\n \r\n "code": "Conflict",\r\n "message": "\r\n \"error\": ***\r\n \"code\": \"MissingSubscriptionRegistration\",\r\n \"message\": \"The subscription is not registered to use namespace 'microsoft.insights'. See https://aka.ms/rps-not-found for how to register subscriptions.\",\r\n \"details\": [\r\n ***\r\n \"code\": \"MissingSubscriptionRegistration\",\r\n \"target\": \"microsoft.insights\",\r\n \"message\": \"The subscription is not registered to use namespace 'microsoft.insights'. See https://aka.ms/rps-not-found for how to register subscriptions.\"\r\n \r\n ]\r\n \r\n"\r\n \r\n ]\r\n \r\n ]\r\n \r\n","code":"Conflict","message":"\r\n "status": "Failed",\r\n "error": ***\r\n "code": "ResourceDeploymentFailure",\r\n "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n "details": [\r\n ***\r\n "code": "DeploymentFailed",\r\n "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",\r\n "details": [\r\n \r\n "code": "Conflict",\r\n "message": "\r\n \"error\": ***\r\n \"code\": \"MissingSubscriptionRegistration\",\r\n \"message\": \"The subscription is not registered to use namespace 'Microsoft.ApiManagement'. See https://aka.ms/rps-not-found for how to register subscriptions.\",\r\n \"details\": [\r\n ***\r\n \"code\": \"MissingSubscriptionRegistration\",\r\n \"target\": \"Microsoft.ApiManagement\",\r\n \"message\": \"The subscription is not registered to use namespace 'Microsoft.ApiManagement'. See https://aka.ms/rps-not-found for how to register subscriptions.\"\r\n ***\r\n ]\r\n \r\n"\r\n \r\n ]\r\n \r\n ]\r\n \r\n"]

Expected/desired behavior

Not a big deal, but if the service is only available in certain regions it may be worth mentioning it in the README

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

It seems once the github action kicks off to update the ARM resources, your container app will be offline/unresponsive until that new revision has fully started up. The previous revision's traffic will be revoked instantly even though the new revision is not ready

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

• Fork repository
• Set environment variables
• Invoke workflow
• Receive error msg

Any log messages given by the failure

ERROR: "code": "InvalidTemplateDeployment", "message": "The template deployment 'main' is not valid according to the validation procedure. The tracking id is 'af20d38b-1053-41f9-8b24-2a7b70cf54c2'. See inner errors for details."

Inner Errors:
"code": "ValidationForMultipleResourcesFailed", "message": "Validation failed for multiple resources. Check 'Error.Details[]' for more information."

Inner Errors:
"code": "ContainerAppImageRequired", "message": "Container with name 'python-app' must have an 'Image' property specified."

Inner Errors:
"code": "ContainerAppImageRequired", "message": "Container with name 'go-app' must have an 'Image' property specified."

Inner Errors:
"code": "ContainerAppImageRequired", "message": "Container with name 'node-app' must have an 'Image' property specified."
Error: Error: az cli script failed.

Expected/desired behavior

Deployment succeeds

OS and Version?

Ubuntu 20.04.4
Runner Version: 2.294.0

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

deploy the services without bicep, but using az cli is not working due to the fact the dapr components.yaml files are not in the supported format

Any log messages given by the failure

Expected/desired behavior

use the components.yaml to deplo with azue cli

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.