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

feat(containers): support Application resource queries #705

Conversation

lusergit
Copy link
Collaborator

Application resource queries are available trough graphql, the frontend can now access an application and all the fields of nested resources

@lusergit lusergit requested a review from noaccOS November 11, 2024 15:31
@lusergit lusergit force-pushed the feat/application-queries branch from 9bafa06 to e19f6fc Compare November 11, 2024 16:14
@lusergit lusergit marked this pull request as ready for review November 12, 2024 08:47
@lusergit lusergit force-pushed the feat/application-queries branch 2 times, most recently from dce605e to 68ee129 Compare November 12, 2024 09:38
`Application` resource queries are available trough graphql, the
frontend can now access an application and all the fields of nested resources

Signed-off-by: Luca Zaninotto <[email protected]>
`Release` resource can be retrieved by id. Closes edgehog-device-manager#699

Signed-off-by: Luca Zaninotto <[email protected]>
@lusergit lusergit force-pushed the feat/application-queries branch from 68ee129 to 5588f7b Compare November 12, 2024 10:17
@noaccOS noaccOS merged commit 4e224ae into edgehog-device-manager:feature/application-management Nov 12, 2024
8 checks passed
@lusergit lusergit linked an issue Nov 12, 2024 that may be closed by this pull request
lusergit pushed a commit to lusergit/edgehog that referenced this pull request Nov 26, 2024
@lusergit lusergit deleted the feat/application-queries branch December 2, 2024 09:57
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.

Ensure that the relevant fields of Releases are accessible by GraphQL
2 participants