-
Notifications
You must be signed in to change notification settings - Fork 22
Issues: edgehog-device-manager/edgehog
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Use server-side pagination for GraphQL queries that return lists
backend
This issue is relative to the Edgehog Backend
enhancement
New feature or request
frontend
This issue is relative to the Edgehog Frontend
Support upgrading an existing app deployment
containers
This issue relates to the container management functionality
frontend
This issue is relative to the Edgehog Frontend
#703
opened Nov 8, 2024 by
davidebriani
Document Application Management feature
containers
This issue relates to the container management functionality
documentation
Improvements or additions to documentation
meta
This issue is a "macro" issue, therefore it depends on a number of tasks
Applications: Credentials page
containers
This issue relates to the container management functionality
frontend
This issue is relative to the Edgehog Frontend
Base Image Deletion Restrictions Linked to OTA Campaigns and Update Channels in Version 0.9
#598
opened Sep 12, 2024 by
FabrizioBenvenuti
Handle CORS requests in the Admin REST API
backend
This issue is relative to the Edgehog Backend
good first issue
Good for newcomers
Distinguish different errors when relating an update channel to target groups
ash-porting
Issues used to track open issues regarding the Ash porting process
enhancement
New feature or request
#529
opened May 27, 2024 by
davidebriani
Reimplement tenant cleanup using Ash
ash-porting
Issues used to track open issues regarding the Ash porting process
Cache Good for newcomers
:last_seen_ip
in the database
good first issue
#489
opened Apr 11, 2024 by
rbino
Rework device attributes
ash-porting
Issues used to track open issues regarding the Ash porting process
Input of GraphQL update mutations should be non-nullable
ash-porting
Issues used to track open issues regarding the Ash porting process
#449
opened Feb 19, 2024 by
szakhlypa
Update the "Publishing Device Data" section
documentation
Improvements or additions to documentation
Verify the distinction between error and failure in the Update Campaign docs
documentation
Improvements or additions to documentation
Expose the associated UpdateCampaign (if any) from an OTA Operation
frontend
This issue is relative to the Edgehog Frontend
good first issue
Good for newcomers
Implement (remote) log collection and visualization
meta
This issue is a "macro" issue, therefore it depends on a number of tasks
#309
opened Jun 22, 2023 by
bettio
Previous Next
ProTip!
What’s not been updated in a month: updated:<2024-11-30.