Skip to content
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

Canr disable Enable Health Probes using AZ CLI #27744

Closed
gsuttie opened this issue Nov 2, 2023 · 4 comments · Fixed by #28432
Closed

Canr disable Enable Health Probes using AZ CLI #27744

gsuttie opened this issue Nov 2, 2023 · 4 comments · Fixed by #28432
Assignees
Labels
Auto-Assign Auto assign by bot bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. Network - Front Door Service Attention This issue is responsible by Azure service team.

Comments

@gsuttie
Copy link

gsuttie commented Nov 2, 2023

Describe the bug

When running the following command it doesn't seem like there is a way to disable the health probe

az afd origin-group create --resource-group $resourceGroupName
--origin-group-name $originGroupName --profile-name $frontDoorName
--probe-request-type GET --probe-protocol Http
--probe-interval-in-seconds 60 --probe-path /
--sample-size 4 --successful-samples-required 3
--additional-latency-in-milliseconds 50 `
--output none

Related command

az afd origin-group create

Errors

No errors but I don't see how to disable the 'Enable Health probes tickbox'

Issue script & Debug output

az afd origin-group create --resource-group $resourceGroupName
--origin-group-name $originGroupName --profile-name $frontDoorName
--probe-request-type GET --probe-protocol Http
--probe-interval-in-seconds 60 --probe-path /
--sample-size 4 --successful-samples-required 3
--additional-latency-in-milliseconds 50 `
--output none

Expected behavior

origin group doesnt have 'Enable Heath probes ticket'

Environment Summary

azure-cli 2.53.1

core 2.53.1
telemetry 1.1.0

Extensions:
account 0.2.5
aks-preview 0.5.149
application-insights 0.1.19
azure-devops 0.26.0
azure-firewall 0.14.8
desktopvirtualization 0.2.0
front-door 1.0.17

Dependencies:
msal 1.24.0b2
azure-mgmt-resource 23.1.0b2

Additional context

No response

@gsuttie gsuttie added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Nov 2, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. Auto-Assign Auto assign by bot Network - Front Door Service Attention This issue is responsible by Azure service team. labels Nov 2, 2023
@yonzhan
Copy link
Collaborator

yonzhan commented Nov 2, 2023

Thank you for opening this issue, we will look into it.

Copy link
Contributor

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @cdnfdsuppgithub, @t-bzhan, @gxue, @TracyYaoYao.

@t-bzhan t-bzhan self-assigned this Nov 23, 2023
@surlypants
Copy link

january 2024 and still impossible? neither az cli nor pwsh

@t-bzhan
Copy link
Contributor

t-bzhan commented Feb 18, 2024

Hi @gsuttie/ @surlypants , that is a bug. We will try to fix it in next release. As a workaround, you could try to use below command as a workaround:

az afd origin-group update --remove "healthProbeSettings" --resource-group bo-private --origin-group-name og111 --profile-name bzhan-test111 --debug

necusjz pushed a commit that referenced this issue Feb 26, 2024
…th-probe` (#28432)

* add enable_health_probe for origin group

* add new parameters

* change para

* change blank value

---------

Co-authored-by: Jingnan Xu <jingnanxu@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Assign Auto assign by bot bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. Network - Front Door Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants