I am back working on our service catalog, and really need a way to access some additional properties
I see that I can add then to a VSM step as 'Extra Information', but not a TEST step
I really want these to the service related, not step related.
anyone come up with a workaround for this kind of solution?
I need version, owner, and maybe some other attributes that I haven't thought of yet
Author, Version, Date modified, service dependencies, ports used, ...
Based on my understanding of your requirement - can you add a step of type "Read Properties from a File" with the property file having all the name value pairs that you need. Place this property file in a subfolder within data folder of a project & make sure the path of the file in the above step has {{LISA_PROJ_ROOT}} as the starting part of the path
thanks, but I probably wasn't clear enough..
I would like to build a catalog of services.. but I want to know the author, date created, version, dependencies, ... and the list goes on..
the service itself won't use these but the catalog inspection/population pgm would..
but the tst's don't have a mandatory config file like the VSEs do.. just trying to find a way to be consistent..
these services will be packaged and stored away from the DT dev environment, so you can't use that to inspect..
for VSM based services, I can use the config file and put in key/value pairs and get to them via some tooling..
what do I do about tst based services.. demand they create a mari to package a config file?