Hi Arpit
Unfortunately I don't think so because configuration are built using Java backend classes annotated with annotations from org.osgi.service.metatype.annotations such as @ObjectClassDefinition to define a configuration and @AttributeDefinition to define an attribute of that configuration
If we look at the @AttributeDefinition documentation we can see that it is processed at compile-time and not run-time, so no possibility for the backend to call an API to populate a list of option
![Selection_055.png Selection_055.png](https://experienceleaguecommunities.adobe.com/t5/image/serverpage/image-id/23075i05A2BAF04B0F712E/image-size/large/is-moderation-mode/true?v=v2&px=999)
The fronted libraries loaded on the configuration page do not come from /libs but from /system/console/res/lib, so it's not possible to override them either.
I'm curious, what's your use-case?