Thanks Darren, this is what I suspected - I'll have to pull the whole server configuration to check which options will affect a single subnet (due to inheritance) - meaning the submet_cmds get hook does not add any efficiency over the whole-file operation.
Might be worth a RFE to filter the output (specify return fields), or to optionally include globally scoped options in the subnet response? How do I go about getting those submitted? Cheers -----Original Message----- From: Darren Ankney <darren.ank...@gmail.com> Sent: 09 May 2025 11:17 To: Kea user's list <kea-users@lists.isc.org> Cc: Matt Crum <matt.c...@pcn-inc.com> Subject: Re: [Kea-users] Kea v3 (2.7.7) - Global options via API Hello, I believe that config-get will be the method you'll have to use to retrieve global settings that don't have a specific api structure (client-classes, shared-networks,subnets, and reservations all have specific API calls, but global settings, hooks, loggers, option-def and data, and many others do not). Thank you, Darren Ankney On Fri, May 9, 2025 at 5:50 AM Matt Crum via Kea-users <kea-users@lists.isc.org> wrote: > > Hi - > > > > We’re developing an API integration with Kea and until now have been doing > whole file operations for everything, because we did not have access to the > subnet/host CMDs hooks. > > > > Now that some of the hooks are being open sourced, we are looking to switch > to using them for our integration to make things more efficient. > > > > One of our requirements is to list DHCP options which will be presented to a > specified host/pool/subnet - I have not been able to find a way to grab > global options using hooks. > > > > Are we aware of a way to either return global DHCP options using hooks, or > (better) to grab a computed configuration for a specified item, combining > global, shared and locally set options? > > > > We can obviously revert to grabbing the whole configuration and parsing it, > but it seems expensive. > > > > Thanks in advance. > > > > CONFIDENTIALITY NOTICE: This message is intended for the use of the > individual or entity to which it is addressed and may contain information > that is confidential, privileged, and exempt from disclosure under applicable > law. If the recipient of this message is not the intended recipient, you are > hereby notified that any reading, printing, copying, dissemination, > distribution, disclosure, or forwarding of this communication is strictly > prohibited. If you have received this communication in error, please contact > the sender immediately and delete it from your system. Thank You. > > --PCNdcV.12 > > -- > ISC funds the development of this software with paid support subscriptions. > Contact us at https://www.isc.org/contact/ for more information. > > To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. > > Kea-users mailing list > Kea-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/kea-users --PCNO365V.12 CONFIDENTIALITY NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged, and exempt from disclosure under applicable law. If the recipient of this message is not the intended recipient, you are hereby notified that any reading, printing, copying, dissemination, distribution, disclosure, or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. --PCNdcV.12 -- ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. Kea-users mailing list Kea-users@lists.isc.org https://lists.isc.org/mailman/listinfo/kea-users
