Closing this, no real benefits and to much effort are required
it's not like we position ourselves as low consumption device. with VPP it will be even worse
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Oct 30 2024
Currently I believe that the GraphQL api doesn't offer much functionality unless that has changed over the most recent 3-4 months. I believe it only had get functions and maybe 2 or 3 set methods. This is blocking the web api as it was decided to use GQL for the API.
@Viacheslav so what is the state of this?
No plans to implement it until we receive a request from a customer
Some GRUB options can certainly be useful. I'm against adding ways to pass completely arbitrary options, though. I'll rename the task to reflect that.
Hey @syncer is this feature being bumped to a future release? I saw the Project tags get swapped to a GA tag (which sounds more official to me) but also a comment of "no business case."
@jestabro, what is the current state of this? Should I mark is resolved or keep it?
This is out of the scope of VyOS
there are many other tools like systemrescuecd and others
Reassigned to @natali-rs1985 ; please ask if any questions.
@syncer yes, thanks.
The only piece missing from the original design of using GraphQL to implement templated high level configurations is: migration of templates, versioned by component version; the recent addition of the convertor of set commands to config trees (T6740) makes this a simpler problem. I will revisit and implement migration of templated configurations.
Upstream bug is still a bug, as long as VyOS includes accel-ppp, it is not RFC compliant - so why close it as Not Applicable? Are there plans to include some other PPPoE server implementation in VyOS?
@jestabro this one is completed?
looks like support request