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

chore(update_channel): better errors #771

Merged

Conversation

lusergit
Copy link
Collaborator

When creating and updating an update channel, target group ids are validated to be available, meaning:

  • they are present in the DB
  • they are not related to any other update channel

closes #529

@coveralls
Copy link

coveralls commented Dec 10, 2024

Pull Request Test Coverage Report for Build b51ed9469c247cec308c7d28166a562aedf5f225-PR-771

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.1%) to 78.313%

Totals Coverage Status
Change from base Build e25b04d0901a73c89d3b135e2715dbe5e3bc9fc4: 0.1%
Covered Lines: 1235
Relevant Lines: 1577

💛 - Coveralls

@lusergit lusergit force-pushed the chore/errors-update-channel branch 2 times, most recently from 158b288 to 7e9c7e0 Compare December 10, 2024 16:41
@lusergit lusergit force-pushed the chore/errors-update-channel branch 3 times, most recently from 0173107 to 332fea1 Compare December 12, 2024 10:10
@lusergit lusergit requested a review from noaccOS December 16, 2024 15:13
@lusergit lusergit marked this pull request as draft January 7, 2025 09:50
@lusergit lusergit force-pushed the chore/errors-update-channel branch 2 times, most recently from c82adb8 to 9a5e7aa Compare January 7, 2025 09:57
@lusergit lusergit force-pushed the chore/errors-update-channel branch 2 times, most recently from d0185aa to ed65535 Compare January 7, 2025 10:42
Copy link
Collaborator

@noaccOS noaccOS left a comment

Choose a reason for hiding this comment

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

The copyright for all modified files needs to be updated

Other than that, lgtm

@lusergit lusergit force-pushed the chore/errors-update-channel branch 2 times, most recently from 38d7e23 to 278b643 Compare January 7, 2025 13:47
@lusergit
Copy link
Collaborator Author

lusergit commented Jan 8, 2025

This depends on ash-project/ash_graphql#257 and ash-project/ash_graphql#253, both have been merged but have yet to be integrated in the next release. When it will be ready we can bump up the ash_graphql and ash version and re open the PR for review.

@lusergit lusergit force-pushed the chore/errors-update-channel branch 3 times, most recently from ca658ed to b51ed94 Compare January 9, 2025 09:34
@davidebriani
Copy link
Collaborator

This depends on ash-project/ash_graphql#257 and ash-project/ash_graphql#253, both have been merged but have yet to be integrated in the next release. When it will be ready we can bump up the ash_graphql and ash version and re open the PR for review.

@lusergit here it is: https://github.com/ash-project/ash_graphql/releases/tag/v1.5.0

When creating and updating an update channel, target group ids are
validated to be available, meaning:
- they are present in the DB
- they are not related to any other update channel

closes edgehog-device-manager#529

Signed-off-by: Luca Zaninotto <[email protected]>
@lusergit lusergit force-pushed the chore/errors-update-channel branch from b51ed94 to 5374612 Compare January 13, 2025 07:50
@lusergit lusergit marked this pull request as ready for review January 13, 2025 07:50
@davidebriani davidebriani merged commit 44777a1 into edgehog-device-manager:main Jan 13, 2025
10 checks passed
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.

Distinguish different errors when relating an update channel to target groups
4 participants