I have some initial PRs [0][1][2] up for using pulplift to create a
development environment for pulp3 as described in 4243. [3] Please take a
look and provide feedback on any changes we might want to make. Feel free
to discuss what we'd like to see here or comment directly on the PRs.
Note, I ha
On Wed, 9 Jan 2019 08:46:18 -0500
David Davis wrote:
> The Rubygems api includes sha as part of the metadata for a gem.
> Couldn't you use that as part of the natural key?
>
> I'm surprised that Chef's supermarket API doesn't include this as
> well. Maybe we could open a feature request?
>
> Da
On Wed, Jan 09, 2019 at 08:46:18AM -0500, David Davis wrote:
>The Rubygems api includes sha as part of the metadata for a gem.
>Couldn't you use that as part of the natural key?
>I'm surprised that Chef's supermarket API doesn't include this as well.
>Maybe we could open a feature r
On Wed, Jan 9, 2019 at 12:30 PM Tatiana Tereshchenko
wrote:
> To summarize where we are so far:
> *All* master/detail related endpoints will be automatically prepended
> with Django app *label* [0]
> - concerns: 'pulp_' in the label
> - options to address concerns:
> * introduce
To summarize where we are so far:
*All* master/detail related endpoints will be automatically prepended with
Django app *label* [0]
- concerns: 'pulp_' in the label
- options to address concerns:
* introduce a new attribute to the AppConfig class to use in the
endpoints constructio
The Rubygems api includes sha as part of the metadata for a gem. Couldn't
you use that as part of the natural key?
I'm surprised that Chef's supermarket API doesn't include this as well.
Maybe we could open a feature request?
David
On Tue, Jan 8, 2019 at 2:50 PM Simon Baatz wrote:
> On 08.01.
I also want to vote for solution 2.
Only thing i want to add is multi-tenancy capability. The repository of
one user should really not be (from a functionality view point)
affected by actions on another repository. Sharing the actual files for
performance is desireable, but sharing content units mi
