[allura:tickets] Re: #8044 API for current site notification

[Dave Brondsema <da...@brondsema.net>]

Standard rest API authorization should work fine.  (It lets oauth or current user session work).

For access/rights, it should be just for the current user.


---

** [tickets:#8044] API for current site notification**

**Status:** in-progress
**Milestone:** unreleased
**Labels:** api sf-current sf-2 42cc 
**Created:** Wed Jan 13, 2016 03:35 PM UTC by Dave Brondsema
**Last Updated:** Thu Jan 21, 2016 07:32 PM UTC
**Owner:** Igor Bondarenko


Expose the current site notification (i.e. `ThemeProvider.get_site_notification` logic) as an API.

The `request.cookies` might be able to stay as it is, but likely should support those values being passed in as regular API params.  The `response.set_cookie` probably should be returned as response values.

Make sure the RAML api docs are updated.


---

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.