[
https://issues.apache.org/jira/browse/KNOX-2053?focusedWorklogId=329060&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-329060
]
ASF GitHub Bot logged work on KNOX-2053:
----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Oct/19 09:11
Start Date: 16/Oct/19 09:11
Worklog Time Spent: 10m
Work Description: smolnar82 commented on issue #164: KNOX-2053 - New REST
API to create/read/update/delete service definitions
URL: https://github.com/apache/knox/pull/164#issuecomment-542606373
@risdenk - I addressed all of your above-comments:
- removed the Guava dependency (created a new utility class to determine if
a Collection is sorted)
- removed the `commons-lang3` dependency by simply implementing the
`toString` method with a `StringBuilder`
- synchronized and reduced visibility of marshaller/unmarshaller access
- changed the responses in the new API
- if successfully processed the `Location` header will indicate the
created/updated resource location
- if failed the error we return starts with a constant
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 329060)
Time Spent: 3h 20m (was: 3h 10m)
> Add Service Definition Management to Admin API
> ----------------------------------------------
>
> Key: KNOX-2053
> URL: https://issues.apache.org/jira/browse/KNOX-2053
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Reporter: Larry McCay
> Assignee: Sandor Molnar
> Priority: Major
> Fix For: 1.4.0
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> Currently, the Admin API allows management and access to topologies,
> descriptors, provider config, etc but does not provide access to the Service
> Definitions for the proxied services.
> Let's expand the API the include to include service defs and allow for
> customization through the API. Changes made via the API will typically
> require a restart and touch of an topology file that is referencing the
> change service def. This may require a separate Jira and effort to address.
> In the meantime, we should be able to change, add and delete service
> definitions including both service and rewrite XML files.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
