SamCooper / COMMON_SPEC_RIDS

1 stars 0 forks source link

Provider level configuration #109

Open lacourte opened 6 years ago

lacourte commented 6 years ago

This issue is a sequel of the Provider vs Service config issue which has been closed. I raise it when I try to use the currently defined concept in the tests. I want to define a single test service provider which is to be managed by the Configuration service. This provider defines 3 services named ConfigurationTestHC (meant to test hard-coded configurations), ConfigurationTestNC (meant to test non-COM configurations), and ConfigurationTest (meant to test COM compliant configurations). In the init phase I create service level configurations for alll 3 services then I try to create a provider level configuration. I have no mean to say that the provider level configuration is a set of chosen service level configurations. I can only get the lists of ConfigurationObjectSet objects from the service level configurations, and mix them to build the provider level configuration. However, as the target service provider, how do I:

  1. find to which service applies each ConfigurationObjectSet object ?
  2. identify the configuration of the ConfigurationTestHC service (which has no associated configuration object) ?

The answer to question 2 is probably that a provider will never mix an hard-coded configuration service with other services. The anwer to question 1 may be that the type of the terminal "service objects" will have to include an identifier of the target service. This would certainly be implemented more efficiently by clearly defining the ProviderConfiguration object as a set of ServiceConfiguration objects.

If you think that my remark makes sense, it might be left as a remark in the yellow book as this change would imply more modifications in our implementations.