feat: use custom cloud init status reporting - #9022
Conversation
…ript Bake experimental_skip_ready_report into VHD via cloud.cfg.d to skip cloud-init's built-in health ready report to Azure fabric. Add a standalone Python script (report_ready.py) that can be invoked from CSE to report ready at the appropriate time during node provisioning. Depends on canonical/cloud-init#6771. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Supersede the single-file DataSourceAzure.py vendoring hack with the actual patched cloud-init Jammy .deb built from https://github.com/peytonr18/cloud-init/tree/probertson/jammy-runtime-ds-options-skip-ready (base version 26.1-0ubuntu1~22.04.1), which carries both the experimental_skip_ready_report patch (canonical/cloud-init#6771) and a second patch allowing datasource options to be overridden at runtime via custom data. Installing the full package via dpkg instead of overwriting a single module keeps cloud-init's schema, tests, and packaging metadata consistent, and avoids the risk of the vendored file drifting from the rest of the installed package. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 9e623d45-e026-4e5c-b9e2-3107c1d96592
Windows Unit Test Results 3 files 12 suites 54s ⏱️ Results for commit 7436e77. |
7436e77 to
a5ac516
Compare
AgentBaker Linux Gate DetectiveRun: https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=174679898 |
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #