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

fix: device list acceptable wrong status #3547

Merged
merged 2 commits into from
Feb 19, 2024

Conversation

henrybarreto
Copy link
Member

No description provided.

@henrybarreto henrybarreto self-assigned this Feb 15, 2024
@henrybarreto henrybarreto force-pushed the fix/device_list_acceptable_no_status branch 3 times, most recently from 8dc41f1 to b6792d3 Compare February 15, 2024 18:54
@henrybarreto henrybarreto marked this pull request as ready for review February 15, 2024 19:06
@henrybarreto henrybarreto requested review from a team as code owners February 15, 2024 19:06
@henrybarreto henrybarreto force-pushed the fix/device_list_acceptable_no_status branch 3 times, most recently from b2fa3d4 to 9772b9a Compare February 15, 2024 23:57
@henrybarreto henrybarreto force-pushed the fix/device_list_acceptable_no_status branch 4 times, most recently from 2372a0b to 69f5bcd Compare February 16, 2024 15:43
When listing devices with a non empty status, i.g `accepted`, `pending`,
the `acceptable` field was right defined. However, if it is set to
empty, no logic was applied, setting the field to `false`, the default
value in Go.

To solve the issue, we evaluate the `acceptable` field based on devices
in `removed_devices`, for cloud instances, its `accepted` status when it
is already `accepted` and when the namespace has a limit defined.

Fixes: #3527
@otavio otavio merged commit cbd2ea2 into master Feb 19, 2024
8 checks passed
@otavio otavio deleted the fix/device_list_acceptable_no_status branch February 19, 2024 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants