Conversation
The inventory plugin moved from datum-cloud/inventory to milo-os/inventory and, with it, to the milo-os naming convention: the binary and its release archives are milo-inventory_*, not datumctl-inventory_*. This entry still pointed at datum-cloud/inventory v0.2.0 -- a build that speaks graph.inventory.miloapis.com/v1alpha2, an API group with no objects in it. Installing from the catalog gave you a plugin that reported an empty system while inventory.miloapis.com/v1alpha1 served 173 live records. Rewrite homepage, version, and all six uri/sha256 pairs. Checksums are from the v0.2.0 release's checksums.txt, spot-verified by downloading and hashing two of the archives. update-plugin-index could not do this itself: it rewrites the version in existing uris and looks the resulting basenames up in checksums.txt, so the rename made every lookup miss. Once this lands the names agree and future releases update automatically. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
This entry points at
datum-cloud/inventoryv0.1.0 — a build that speaksgraph.inventory.miloapis.com/v1alpha2, an API group that has never held a single object. Installing the plugin from this catalog gives you a CLI that reports an empty system:…while
inventory.miloapis.com/v1alpha1serves 173 live records (Region 19, Site 20, Cluster 20, Node 110, Provider 4).The plugin has moved to
milo-os/inventory, joiningipamandsearchin shipping from its service repo, and now speaks v1alpha1 again.What
Rewrite
plugins/inventory.yaml:homepage→https://github.com/milo-os/inventoryversion→v0.2.0uri/sha256pairs → themilo-inventory_*assetsThe archive basenames change with the repo, because milo-os names plugin binaries
milo-<service>(milo-ipam,milo-search) where datum-cloud usesdatumctl-<service>.Also adds the two-line header comment
ipam.yamlandsearch.yamlcarry, and quotes thesha256values to match them.Why this is manual
update-plugin-indexran on the v0.2.0 release and failed:The action bumps the version inside the existing URIs and looks the resulting basenames up in
checksums.txt. It cannot re-derive a filename or a homepage, so the rename made every lookup miss. Once this lands the names agree and future releases update automatically — no further manual edits.The app token worked fine; this was purely the rename.
Verification
Checksums come from the v0.2.0 release
checksums.txt, generated into the manifest programmatically rather than transcribed. Two archives were independently downloaded and re-hashed:Both match.
After merge
Until then, installing by owner/repo works and bypasses the catalog:
Context: milo-os/inventory#50.
🤖 Generated with Claude Code