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.

Sign up for GitHub

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

Jump to bottom

[docs] Inconsistencies between Creating an Update Channel-Target Groups doc and actual behaviour #339

Open
harlem88 opened this issue Jul 26, 2023 · 1 comment · May be fixed by #776
Open

[docs] Inconsistencies between Creating an Update Channel-Target Groups doc and actual behaviour #339

harlem88 opened this issue Jul 26, 2023 · 1 comment · May be fixed by #776
Assignees
@lusergit
Milestone
v0.10

Comments

@harlem88
Copy link
Contributor

harlem88 commented Jul 26, 2023 •
edited
Loading

Currently in the Creating an Update Channel section of managed-ota-updates page the Target Groups is declared as an optional field, but in the Fronted page (/update-channels/new) of Edgehog Create Update Channel the field is declared as Required
Screenshot_20230726_125831
@rbino rbino added this to the v0.9 milestone Apr 19, 2024
@davidebriani
Copy link
Collaborator

See also the discussion about at least one target group being required or not: #518

@davidebriani davidebriani modified the milestones: v0.9, v0.10 Dec 3, 2024
@lusergit lusergit linked a pull request Dec 13, 2024 that will close this issue
Open
@lusergit lusergit self-assigned this Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lusergit lusergit

Labels
None yet
Projects
None yet
Milestone
v0.10
Development

Successfully merging a pull request may close this issue.

feat(update_channel) allow update channels to have 0 update groups lusergit/edgehog
4 participants
@harlem88 @rbino @lusergit @davidebriani