|
Date: Tue, 13 Jan 2015 00:34:55 +0100
|
|
From: rbarlow@redhat.com
|
|
To: dropbox+pulp+c71e@plan.io
|
|
Message-ID: <54b45a1f3324_4db13fe180e7fea46857b@apollo.mail>
|
|
in-reply-to: redmine.journal-217.20150112231909@plan.io
|
|
Subject: Re: [Pulp - Story #86] As a user, I can add mutable custom metadata
|
|
to a unit
|
|
Mime-Version: 1.0
|
|
Content-Type: multipart/mixed;
|
|
boundary=aCfPvKmc5Ggc1Q4Lh9iGWj1gNS7weXBM8;
|
|
charset=UTF-8
|
|
Content-Transfer-Encoding: 7bit
|
|
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23
|
|
X-HE-Spam-Level: -----
|
|
X-HE-Spam-Score: -5.0
|
|
X-HE-Spam-Report: Content analysis details: (-5.0 points) pts rule name
|
|
description ---- ----------------------
|
|
-------------------------------------------------- -5.0 RCVD_IN_DNSWL_HI RBL:
|
|
Sender listed at http://www.dnswl.org/, high trust [209.132.183.28 listed in
|
|
list.dnswl.org]
|
|
X-HE-SPF: PASSED
|
|
|
|
|
|
--aCfPvKmc5Ggc1Q4Lh9iGWj1gNS7weXBM8
|
|
Content-Type: text/plain;
|
|
charset=utf-8
|
|
Content-Transfer-Encoding: quoted-printable
|
|
|
|
On 01/12/2015 06:19 PM, Chris Duryee wrote:
|
|
> will there be enforcement of how much data can be stored in there?
|
|
|
|
I am not planning on enforcing anything about the request outside of
|
|
requiring the usual UPDATE permission bit. Mongo itself will reject the
|
|
data if it goes over its limit (16 MB I believe). I'm planning to make
|
|
it so this API can only do HTTP 200, 403, and 404 with a PUT request to
|
|
something like:
|
|
|
|
/content/units/<UUID>/user_metadata/
|
|
|
|
Any user that's allowed to UDPATE that URL can overwrite the
|
|
user_metadata field for an already existing UUID. No validation of any
|
|
kind will be provided.
|
|
|
|
Does that sound reasonable?
|
|
|
|
> --- Please write your response above this line ---
|
|
> =
|
|
|
|
> Issue #86 has been updated by Chris Duryee.
|
|
> =
|
|
|
|
> will there be enforcement of how much data can be stored in there?
|
|
> =
|
|
|
|
> -----------------------------------------------------------------------=
|
|
-
|
|
> =
|
|
|
|
> =
|
|
|
|
> Story #86: As a user, I can add mutable custom metadata to a unit
|
|
> <https://pulp.plan.io/issues/86#change-217>
|
|
> =
|
|
|
|
> * Author: Michael Hrivnak
|
|
> * Status: ASSIGNED
|
|
> * Priority: High
|
|
> * Assignee: Randy Barlow
|
|
> * Category:
|
|
> * Sprint/Milestone: January 2015
|
|
> * Complexity: 8
|
|
> * Bugzilla link: =
|
|
|
|
> =
|
|
|
|
> When using pulp as a data source for another application, like a websit=
|
|
e
|
|
> or even a web UI, it would be very useful for the user to have a blob o=
|
|
f
|
|
> metadata on each unit that they can manipulate. The "user" in this case=
|
|
|
|
> might be the web app itself.
|
|
> =
|
|
|
|
> Deliverables
|
|
> =
|
|
|
|
> * add a blob to the unit data model
|
|
> * make that blob readable and mutable through the REST API
|
|
> * REST API docs
|
|
> * release notes
|
|
> =
|
|
|
|
> -----------------------------------------------------------------------=
|
|
-
|
|
> =
|
|
|
|
> You have received this notification because you have either subscribed
|
|
> to or are involved in a project on pulp Planio.
|
|
> To change your notification preferences, please click here:
|
|
> https://pulp.plan.io/my/account
|
|
> =
|
|
|
|
> =
|
|
|
|
> =
|
|
|
|
> This notification was cheerfully delivered by <https://plan.io/>
|
|
> =
|
|
|
|
> Planio <https://plan.io/>
|
|
> =
|
|
|
|
|
|
|
|
--aCfPvKmc5Ggc1Q4Lh9iGWj1gNS7weXBM8--
|
.