Describe the bug
When setting a A or AAAA record the CLI returns before the record is publicly visible.
A workaround would be a flag like --await-propagated
Related command
az network dns record-set a add-record ...
Errors
No error, just bad behaviour
Issue script & Debug output
Records don't show up fast enough
Expected behavior
The DNS should answer with the new record immediately after the command returns.
Environment Summary
azure-cli 2.51.0
core 2.51.0
telemetry 1.1.0
Dependencies:
msal 1.24.0b1
azure-mgmt-resource 23.1.0b2
Python location '/opt/az/bin/python3'
Extensions directory '/home/stefan/.azure/cliextensions'
Python (Linux) 3.10.10 (main, Jul 27 2023, 07:10:25) [GCC 11.3.0]
Legal docs and information: aka.ms/AzureCliLegal
Your CLI is up-to-date.
Additional context
No response
Describe the bug
When setting a A or AAAA record the CLI returns before the record is publicly visible.
A workaround would be a flag like
--await-propagatedRelated command
az network dns record-set a add-record ...
Errors
No error, just bad behaviour
Issue script & Debug output
Records don't show up fast enough
Expected behavior
The DNS should answer with the new record immediately after the command returns.
Environment Summary
azure-cli 2.51.0
core 2.51.0
telemetry 1.1.0
Dependencies:
msal 1.24.0b1
azure-mgmt-resource 23.1.0b2
Python location '/opt/az/bin/python3'
Extensions directory '/home/stefan/.azure/cliextensions'
Python (Linux) 3.10.10 (main, Jul 27 2023, 07:10:25) [GCC 11.3.0]
Legal docs and information: aka.ms/AzureCliLegal
Your CLI is up-to-date.
Additional context
No response