[
https://issues.apache.org/jira/browse/YUNIKORN-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17247983#comment-17247983
]
Sunil G commented on YUNIKORN-418:
----------------------------------
By looking at the REST definition, my suggestion will be like this,
# *GET*: Get a cluster config
# *PUT*: Update a config property or set of config items (This will be
idempotent)
# *POST*: This is to create a new configuration object itself (This will NOT
be idempotent). We can add a query param called (dry_ru) to do any validations
on config.
This may be closer to a cleaner REST model, however we can see how best we can
match to pure REST way or not. my $0.02 cents.
> Add "config" REST API
> ---------------------
>
> Key: YUNIKORN-418
> URL: https://issues.apache.org/jira/browse/YUNIKORN-418
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Reporter: Manikandan R
> Assignee: Manikandan R
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
