ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Speidel (JIRA)" <>
Subject [jira] [Resolved] (AMBARI-4277) Update '/stacks' endpoint to use the api framework
Date Tue, 14 Jan 2014 20:07:23 GMT


John Speidel resolved AMBARI-4277.

    Resolution: Fixed

committed to trunk

> Update '/stacks' endpoint to use the api framework
> --------------------------------------------------
>                 Key: AMBARI-4277
>                 URL:
>             Project: Ambari
>          Issue Type: Improvement
>            Reporter: John Speidel
>            Assignee: John Speidel
>         Attachments: AMBARI-4277.patch
> Part of the work being done to implement blueprints.
> As a result of the blueprint work, the stacks api will be exposed to users and therefore
needs to be updated to use the api framework to be consistent with the other api endpoints.
> We currently have '/stacks' and '/stacks2' endpoints. The '/stacks' endpoint is very
old and doesn't use the api framework and is inconsistent with the rest of the api. This endpoint
isn't used by the UI or any other internal component and has never been documented. The 'stacks2'
endpoint does use the api framework and is consistent with the other endpoints in it's usage
except for the naming of the endpoint and some of it's children. This endpoint is currently
used by the UI.
> This task will basically clone the functionality of the 'stacks2' endpoint in the 'stacks'
endpoint. The 'stacks' endpoint will be augmented with additional information in future tasks
as needed by blueprints. Examples are component dependencies and topology tokens in config
properties. After this work the 'stacks2' endpoint should basically be deprecated and the
UI should eventually be phased over to the new 'stacks' endpoint.

This message was sent by Atlassian JIRA

View raw message