Using LDAP as a general data store (as a replacement for SQL/nosql)

So I had an interesting talk today with some coworkers regarding spitballing ideas for some infrastructure we are building. The topic of concern is the aspect of using LDAP as a generic data store. My coworker insists that this is a good idea. I’m familiar with the concept of LDAP for auth purposes, but the aspect of using it as a general data store for users in addition to accounts, services, billing data, machine inventory; and all sorts of things that a company involved with selling cloud servers/services would need to store. I can’t seem to find any real world instances of this sort of use case. I will admit that much of the data would be hierarchical, but not necessarily all. Is this a good idea™️? Looking for some answers from people in the know, not people telling me that ldap is used for user data - I know that. As a seasoned MySQL user, this seems crazy to me, but I’m an open minded person. I’m looking for some honest and thoughtful answers. Should we consider using this for storing all sorts of data, should we only use it for storing user credentials for logins to our systems, or should we use a mainstream database for both things (obviously with hashed/salted passwords, although we may want to lean on hashicorp vault for that purpose)? Thank you!