Skip to content

feat: use custom cloud init status reporting#9022

Draft
lilypan26 wants to merge 3 commits into
mainfrom
lily/custom-cloud-init-reporting
Draft

feat: use custom cloud init status reporting#9022
lilypan26 wants to merge 3 commits into
mainfrom
lily/custom-cloud-init-reporting

Conversation

@lilypan26

Copy link
Copy Markdown
Contributor

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

awesomenix and others added 3 commits July 23, 2026 13:24
…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
@lilypan26 lilypan26 changed the title Lily/custom cloud init reporting feat: use custom cloud init status reporting Jul 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants