Should a config management service provider indicate the types of configuration items it selects?

    • Hide

      Close with no change to the specification.

      Show
      Close with no change to the specification.
    • Hide

      As per discussion in meeting on 2016/05/19, there is no currently known business case requiring a configuration to declare a set of possible selected artifact types. Maintaining and publishing such a list per configuration could be burdensome. Publishing such a list at the service or service provider level might make more sense in some cases, but would be difficult for more dynamic providers, or those with extensible type systems.

      Show
      As per discussion in meeting on 2016/05/19, there is no currently known business case requiring a configuration to declare a set of possible selected artifact types. Maintaining and publishing such a list per configuration could be burdensome. Publishing such a list at the service or service provider level might make more sense in some cases, but would be difficult for more dynamic providers, or those with extensible type systems.

      The current draft spec has no feature that allows a client to determine the type or types of resources that might be contained in a configuration from a given service provider - as far as OSLC Config Mgmt is concerned, a configuration might select resources of any type.

      This could be seen as a positive - providers are open to add new resources of any type at any time with no change to their service provider or service information. However, it does not help a client determine if a given configuration or configuration provider is one that contains a specific type of artifact, and such information might be useful in filtering selection dialogs, queries, etc.

            Assignee:
            Unassigned
            Reporter:
            Nick Crossley (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: