@Austin, do we want to update the etherpad since jwt work was merged?
Regards,
Ina Panova
Software Engineer| Pulp| Red Hat Inc.
"Do not go where the path may lead,
go instead where there is no path and leave a trail."
On Mon, Oct 9, 2017 at 2:34 PM, Austin Macdonald wrote:
> Lucki
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 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.
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
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 wrote:
> I think we are ready to start considering an alpha for our REST API.
Just to support what's been said:
User-scheduled actions are definitely out for pulp 3. We'll encourage other
ways of accomplishing that. In the Foreman environment for example, they
already have their own scheduler to use.
When a user requests a task to be run, Pulp will still run it in a simila
On Thu, Oct 5, 2017 at 2:16 PM, Jeremy Audet wrote:
> I don't see any API endpoints for getting JWT tokens. How will
> authorization be handled?
>
I made this list by looking through the schema at http://pulphost/v3/ so it
only includes endpoints that already exist. JWT hasn't been merged yet [0
Oh right I didn't mention those, thanks for asking. Scheduled calls are
also not in Pulp3. I think that was only written about here [1].
[1]: http://pulpproject.org/2016/10/31/pulp-3.0-mvp/
On Thu, Oct 5, 2017 at 2:33 PM, Og Maciel wrote:
> On Thu, Oct 5, 2017 at 2:31 PM, Brian Bouterse
> wrot
JWT auth is landing with this PR [0] which is ready for merging! If we can
merge it tomorrow then it could be included in the next published alpha on
Monday.
@Og, I think the plan is that Pulp3 won't manage consumers anymore so the
/consumers/ API endpoint wouldn't be there.
[0]: https://github.c
Ahh thank you both Austin and Brian :)
--
Og Maciel
Senior Manager, Quality Engineering
Red Hat, Inc.
irc: omaciel
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev
Yes scheduled actions are out. The reasoning is that other tools can manage
the schedule and run commands against the Pulp API and get the same
outcome. Those other tools are offering scheduling so much better than we
were offering that feature.
On Thu, Oct 5, 2017 at 2:20 PM, Austin Macdonald wr
On Thu, Oct 5, 2017 at 2:31 PM, Brian Bouterse wrote:
> @Og, I think the plan is that Pulp3 won't manage consumers anymore so the
> /consumers/ API endpoint wouldn't be there.
Thanks Brian, but what about other tasks that created scheduled actions?
--
Og Maciel
Senior Manager, Quality Engineeri
I don't think there are any actions which can schedule tasks in Pulp 3. Any
requests that trigger a task will return a url for that task.
On Thu, Oct 5, 2017 at 2:25 PM, Og Maciel wrote:
> On Thu, Oct 5, 2017 at 2:20 PM, Austin Macdonald
> wrote:
> > Schedule actions are also out of Pulp 3 (I t
On Thu, Oct 5, 2017 at 2:20 PM, Austin Macdonald wrote:
> Schedule actions are also out of Pulp 3 (I think). There is a generic tasks
> api, which already includes start and finish times.
Interesting. So when I POST some action which would schedule a task
(can't think of one right now), would the
Consumers are not going to be a part of Pulp 3 (except for calculating
applicability), so we don't need to worry about #3041 regarding Pulp3.
On Thu, Oct 5, 2017 at 2:01 PM, Og Maciel wrote:
> I'd like to recommend https://pulp.plan.io/issues/3041 for
> consideration and inclusion soon-ish for n
+1 to working towards a REST API alpha overall. I am happy enough with the
URLs structure. FYI I think the status API is missing from there maybe.
Is it possible for us to get the API docs auto generating and posted online
in the nightly docs? That way as we continue to change them, the nightly
do
I don't see any API endpoints for getting JWT tokens. How will
authorization be handled?
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev
Schedule actions are also out of Pulp 3 (I think). There is a generic tasks
api, which already includes start and finish times.
{
"_href": "
http://pulp3.dev:8000/api/v3/tasks/8a1fc85f-6f74-47b0-b47a-fc5e468ca095/";,
"error": null,
"finished_at": "2017-10
On Thu, Oct 5, 2017 at 2:13 PM, Austin Macdonald wrote:
> Consumers are not going to be a part of Pulp 3 (except for calculating
> applicability), so we don't need to worry about #3041 regarding Pulp3.
But isn't the Task api generic and includes other types of scheduled actions?
--
Og Maciel
Se
I'd like to recommend https://pulp.plan.io/issues/3041 for
consideration and inclusion soon-ish for new API.
--
Og Maciel
Senior Manager, Quality Engineering
Red Hat, Inc.
irc: omaciel
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.co
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
20 matches
Mail list logo
