Forum Discussion

FrankG's avatar
FrankG
3 years ago

Is there a way to use the API to export all PropertySources (like you can with DataSources)?

I'd like to take an occasional backup of all the PropertySources so we can track changes and be able to fail back easily. Is there a way to do this via the API today? Similar to this - ht...
  • mnagel's avatar
    mnagel
    3 years ago

    Yes, they can be exported, but not AFAIK as XML.  We use a script to backup (and track via git) pretty much everything in LM including those.  Our script also has a check mode to validate various endpoints that otherwise fail silently (like busted widgets) and tend to otherwise show up in embarrassing situations, like review meetings with clients.

    This is the profile we use to get propertysources: 

        "/setting/propertyrules"            => { file => "propertysources",
                                             saveoptions => { mode => "oneperfile", format => "dumper" },
                                           },

     

    It might be an undocumented endpoint, not recalling at the moment :).

    Mark

mnagel's avatar
mnagel
Icon for Professor rankProfessor
3 years ago

With most of the undocumented endpoints, you need to use API version 3, not 2.  I usually have to find this along with the endpoint in the browser developer mode (under the Network tab).  I have seen no updates in the API in a while, not sure who is in charge of it now after the last API developer left LM, I am sure it must be someone.

Here is what we have in our API code currently:

        elsif ($path =~ m{^/setting/(oids|functions|configsources|eventsources|propertyrules|batchjobs|topologysources|registry|alert/(dependencyrules|rules)|companySetting)\b}) {
            $version = 3;
        }

This kind of stuff is why I refuse to write API code in Groovy modules until LM supports code libraries within the system.