Open cilerler opened 3 years ago
Hey @cilerler, Thanks for pointing this out. As of now, this action only supports Public IP scenario. Updated : https://github.com/Azure/aci-deploy/blob/master/action.yml#L69 Supporting Private IP will be taken up as an enhancement.
Are you sure that you don't want to mark it as "Bug" since it allows you to set a value, but then it throws an error?
I mean, it literally throws an error if you set Private
; to me, it means a bug
and not an enhancement
.
Since we are calling out explicitly in the action ReadMe as well as action.yml that Private IP scenario is not supported, we'll be taking this as an enhancement.
This issue is idle because it has been open for 14 days with no activity.
I am also having this issue. Is there some reason why Private IP addresses is not supported? Any idea on the timeline on this? Are y'all accepting PRs?
This issue is idle because it has been open for 14 days with no activity.
@zmckinnon We are accepting PRs. We will be glad to accept contributions.
This issue is idle because it has been open for 14 days with no activity.
Is there a reason for this restriction? In Azure Portal it's absolutely possible to create a container instance without a dns label name and a private IP address. I'm curious. :)
Tested it. There's no reason. Sent a PR. :)
This issue is idle because it has been open for 14 days with no activity.
any updates on this issue?
Setting below
throws the error below
and removing
dns-name-label
throws the error below