-
Notifications
You must be signed in to change notification settings - Fork 58
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
Add support for using a configuration file #63
Comments
@kanika1894 is this something being put into production? I need the ability to add more than one volume |
This issue is idle because it has been open for 14 days with no activity. |
Can this be prioritized? Currently the action is very limited because for example we cannot deploy sidecar containers and have to use the CLI way instead. |
This issue is idle because it has been open for 14 days with no activity. |
You can leverage that option using |
The Problem
This action adds support for the basic Azure CLI deploy commands. However, there are some circumstances like supporting multiple volumes or configuring the container's resources (CPU, RAM) where the Azure CLI, and therefore this action, are unable to address.
The Azure CLI solves these limitations using the file configuration option
# Deploy with YAML template az container create --resource-group myResourceGroup --file deploy-aci.yaml
The solution
Add support for the file configuration in this action.
https://docs.microsoft.com/en-us/azure/templates/microsoft.containerinstance/containergroups?tabs=json
Related Issues
#62
The text was updated successfully, but these errors were encountered: