Skip to content

Exclude default silo from utilization response#8461

Merged
david-crespo merged 3 commits into
mainfrom
exclude-default-silo-util
Jun 26, 2025
Merged

Exclude default silo from utilization response#8461
david-crespo merged 3 commits into
mainfrom
exclude-default-silo-util

Conversation

@david-crespo

Copy link
Copy Markdown
Contributor

Closes #5731

@david-crespo david-crespo marked this pull request as ready for review June 26, 2025 21:39
// solution will be to eliminate the default silo altogether, but this
// is dramatically easier.
// See https://github.com/oxidecomputer/omicron/issues/5731
.filter(dsl::silo_id.ne(DEFAULT_SILO_ID))

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is, uh, the whole thing

.authn_as(AuthnMode::SiloUser(user1.id))
.execute()
.await
.expect("failed to create instance in test-suite-silo");

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

arguably this is kind of unnecessary since we do it with default-silo and the individual silo utilization response below, but I really wanted to exercise the list response

@karencfv karencfv left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks!

@david-crespo david-crespo merged commit 5260a19 into main Jun 26, 2025
16 checks passed
@david-crespo david-crespo deleted the exclude-default-silo-util branch June 26, 2025 23:51
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.

Prevent default silo from showing up in utilization response

2 participants