[OASIS Issue Tracker] (OSLCCCM-22) Provide a way for a client to discover the configuration used to resolve a request

From
OASIS Issues Tracker <>
Date
2016-06-02T14:50:51+00:00
ID
Thread
[OASIS Issue Tracker] (OSLCCCM-22) Provide a way for a client to discover the configuration used to resolve a request
[ https://issues.oasis-open.org/browse/OSLCCCM-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62582#comment-62582 ] 

James Amsden commented on OSLCCCM-22:
-------------------------------------

But isn't configuration contribution a baseline, stream or change set, not individual components? Isn't the user interested in the stream contribution, not the individual components in the stream?

> Provide a way for a client to discover the configuration used to resolve a request
> ----------------------------------------------------------------------------------
>
>                 Key: OSLCCCM-22
>                 URL: https://issues.oasis-open.org/browse/OSLCCCM-22
>             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
>          Issue Type: Improvement
>          Components: Configuration Management
>            Reporter: Nick Crossley
>            Assignee: Nick Crossley
>            Priority: Minor
>              Labels: work_required
>
> The spec allows a client to provide a configuration context using either a header or a query string, but there is no way for the client to discover if this configuration was actually used, or which contribution to a global configuration was used, to satisfy the request.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)