Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[nexus] move inventory collection IDs to TypedUuid #5517

Merged

Conversation

sunshowers
Copy link
Contributor

@sunshowers sunshowers commented Apr 12, 2024

Quite mechanical in the end -- just updating types everywhere.

Created using spr 1.3.6-beta.1
@sunshowers sunshowers changed the title move inventory collection IDs to TypedUuid [nexus] move inventory collection IDs to TypedUuid Apr 12, 2024
@sunshowers sunshowers merged commit fc4e127 into main Apr 12, 2024
22 checks passed
@sunshowers sunshowers deleted the sunshowers/spr/move-inventory-collection-ids-to-typeduuid branch April 12, 2024 17:54
jgallagher added a commit that referenced this pull request Apr 12, 2024
Related to #5517 (and might have some small conflicts, but happy to
settle those once it lands).
sunshowers added a commit that referenced this pull request Apr 15, 2024
I wanted to understand how internal DNS works wrt the reconfigurator, so
I tried to port it over to using TypedUuid to basically get an overview
via compile errors. Here's the result.

I realized that we actually were overloading the `Host::Zone`'s ID to
mean either the sled ID (for dendrite) or the zone ID (for the `Other`
variant). I've addressed that in the PR by making the variant also carry the ID.
(This was always an expected outcome of the transition to typed UUIDs -- if we
really are storing more than one kind of UUID within a field, we should make
that clear by specifying our own enum variants.)

Probably depends on #5517 due to shared imports.
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