felipementel is testing out Azure Container Apps GitHub Actions 🚀 #18
felipementelAzureContainerApp.yaml
on: workflow_dispatch
Matrix: build
deploy
53s
Annotations
14 warnings
|
build (8.0.x)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build (8.0.x)
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
build (8.0.x)
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
build (8.0.x)
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
build (8.0.x)
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
build (7.0.x)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build (7.0.x)
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
build (7.0.x)
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
build (7.0.x)
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
build (7.0.x)
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
deploy
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
deploy
Unexpected input(s) 'env', valid inputs are ['appSourcePath', 'acrName', 'acrUsername', 'acrPassword', 'registryUrl', 'registryUsername', 'registryPassword', 'azureCredentials', 'imageToBuild', 'imageToDeploy', 'dockerfilePath', 'containerAppName', 'resourceGroup', 'containerAppEnvironment', 'runtimeStack', 'builderStack', 'targetPort', 'location', 'environmentVariables', 'ingress', 'yamlConfigPath', 'disableTelemetry']
|
|
deploy
Unexpected input(s) 'env', valid inputs are ['appSourcePath', 'acrName', 'acrUsername', 'acrPassword', 'registryUrl', 'registryUsername', 'registryPassword', 'azureCredentials', 'imageToBuild', 'imageToDeploy', 'dockerfilePath', 'containerAppName', 'resourceGroup', 'containerAppEnvironment', 'runtimeStack', 'builderStack', 'targetPort', 'location', 'environmentVariables', 'ingress', 'yamlConfigPath', 'disableTelemetry']
|
|
deploy
Unexpected input(s) 'env', valid inputs are ['appSourcePath', 'acrName', 'acrUsername', 'acrPassword', 'registryUrl', 'registryUsername', 'registryPassword', 'azureCredentials', 'imageToBuild', 'imageToDeploy', 'dockerfilePath', 'containerAppName', 'resourceGroup', 'containerAppEnvironment', 'runtimeStack', 'builderStack', 'targetPort', 'location', 'environmentVariables', 'ingress', 'yamlConfigPath', 'disableTelemetry']
|