Luckily, I wrote this as a text file. http://pad-theforeman.rhcloud.com/p/Pulp3_REST_API
On Mon, Oct 9, 2017 at 8:19 AM, Brian Bouterse <bbout...@redhat.com> wrote: > That server was migrated. Most urls should still exist but now its over > here: http://pad-theforeman.rhcloud.com/ > > This etherpad I think is lost. Any edits from Oct 2 - Oct 6th were lost in > the transition. I lost a bunch of stuff in other etherpads during that time > too. > > -Brian > > > On Sun, Oct 8, 2017 at 11:59 PM, Michael Hrivnak <mhriv...@redhat.com> > wrote: > >> This etherpad deployment has been returning 503s for a few days. Any >> chance you could easily re-generate that list of endpoints with methods and >> put it somewhere else? >> >> On Thu, Oct 5, 2017 at 12:49 PM, Austin Macdonald <aus...@redhat.com> >> wrote: >> >>> I think we are ready to start considering an alpha for our REST API. >>> (REST API and plugin API are versioned separately.) I've started a list of >>> all our endpoints along with accepted methods and the expected responses. I >>> hope this list will be useful for QE as well. >>> >>> http://pad-katello.rhcloud.com/p/pulp3_REST_API >>> >>> The questions that I have: >>> >>> 1. Which other endpoints do we need to add before an alpha of the >>> REST API? (Publications?) >>> 2. Are we happy with the general structure? >>> 3. What else should we do before we call it an alpha? >>> >>> >> >> >> -- >> >> Michael Hrivnak >> >> Principal Software Engineer, RHCE >> >> Red Hat >> > >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev