Summary
Pure docs. The event (ExtensionRunEvent in internal/tracing/events/events.go) already exists but isn't covered in the tracing reference (cli/azd/docs/tracing-in-azd.md), so contributors don't know it's there.
Same goes for the rest of the ext.* family (ext.install, ext.upgrade, ext.promote) and our error.* attribute conventions.
What to do
Add a short table of attributes and a sample row for each event. Cover:
ext.run (extension run lifecycle)ext.install / ext.upgrade / ext.promote (extension management)hooks.exec (hook execution — already partially documented, fill in any gaps)error.* attribute conventions used across azd
Out of scope
Adding new events. This is documentation only.
Summary
Pure docs. The event (
ExtensionRunEventininternal/tracing/events/events.go) already exists but isn't covered in the tracing reference (cli/azd/docs/tracing-in-azd.md), so contributors don't know it's there.Same goes for the rest of the
ext.*family (ext.install,ext.upgrade,ext.promote) and ourerror.*attribute conventions.What to do
Add a short table of attributes and a sample row for each event. Cover:
ext.run(extension run lifecycle)ext.install/ext.upgrade/ext.promote(extension management)hooks.exec(hook execution — already partially documented, fill in any gaps)error.*attribute conventions used across azdOut of scope
Adding new events. This is documentation only.