[Issue-1402] - adds profile list to GET parameters response to help identify orphan…#1621
Conversation
|
Refer to this link for build results (access rights to CI server needed): |
db9561a to
19aaf2c
Compare
6d1d1f8 to
b7bd445
Compare
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
8eb4b76 to
92222d1
Compare
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
This looks good, I tested the sql locally. |
67825fe to
5c21ce1
Compare
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
dangogh
left a comment
There was a problem hiding this comment.
new entry in parameters JSON endpoint justifies moving to API version 1.3. However, profileList should just be profiles, and should be an array of profile names rather than comma-separated list. That makes it easier on the client to do something meaningful with the list.
… as well as quickly show the profiles attached to a param
5c21ce1 to
ffaa8b0
Compare
|
Refer to this link for build results (access rights to CI server needed): |
…ed parameters easily
fixes #1402
fixes #1363