integration-service

[unbreakabl3]

Hello everyone,

I recently created a new TS-based project and noticed a new configuration called integration-service. However, I couldn’t find any information about it in the documentation. Could anyone please explain what this configuration does?

[unbreakabl3]

And what is classes? :)

[unbreakabl3]

Hello everyone,

I recently created a new TS-based project and noticed a new configuration called integration-service. However, I couldn’t find any information about it in the documentation. Could anyone please explain what this configuration does?

OK. I guess this IntegrationService1.conf.ts is a configuration element, which previously was in the element folder, right? If so, is that okay that it is now located in the root of src?

[VenelinBakalov]

Hi @unbreakabl3 , we were recently updating some outdated archetypes and together with that update we proposed a new sample structure for the TS-based projects. The structure is based on services (NsxService, VcenterService) which are in separate folder structure (in the archetype's case it is integration-service-1) and all the related components are nested inside. The underlying separation of folders of course can be optional and based on the amounts of components - e.g. if you have only 1 class you can also put it directly under the root folder of the service. For that matter the configuration element and the accessor (class that accesses the config element and it's data) are placed in the root service folder since it is expected that there will be only a single configuration element holding all values related to that service. On the other hand, there might be multiple actions, classes, resource elements and so on.
But this is just an idea for restructuring, it is not something mandatory and the content inside the archetype is entirely a sample so the project can be adjusted to one own's convention after creation. We decided to update it with a proposed structure that is consistent across a design that can be used to separate functionalities based on products or a specific function (utility, rest-api, etc.) that are separated into services.

[VenelinBakalov]

@unbreakabl3 feel free to re-open the topic in case you have more questions :)