Re: [Pulp-dev] Unified interface for plugin actions

The v3/actions would not need to be limited to plugins, but I think we ought to leave object CRUD how it is. So asynchronous object create/update/delete should remain on the object viewset. The only endpoints I'd like to move are sync, publish, export, and plugin-defined actions like one-shot uplo

Re: [Pulp-dev] Unified interface for plugin actions

I'm curious about how these "actions" are defined. Is the /v3/actions/ namespace limited to plugins? Or, for example, should distribution create/update/delete be nested under /v3/actions/? What about repository create/update/delete? David On Fri, Mar 1, 2019 at 9:08 PM Justin Sherrill wrote: >

Re: [Pulp-dev] Unified interface for plugin actions

On 3/1/19 2:45 PM, Robin Chan wrote: Justin, Would such a change make a significant difference in the effort, complexity, or time to migrate existing (or support new) plugins in Katello? It would be a very small and simple change. Robin On Fri, Mar 1, 2019 at 2:00 PM Justin Sherrill

Re: [Pulp-dev] Unified interface for plugin actions

Justin, Would such a change make a significant difference in the effort, complexity, or time to migrate existing (or support new) plugins in Katello? Robin On Fri, Mar 1, 2019 at 2:00 PM Justin Sherrill wrote: > To me this makes a lot of sense, allows for plugin flexibility, and is > more consi

Re: [Pulp-dev] Unified interface for plugin actions

+1 to what Justin said. I think it's a huge benefit to have the differences between plugins show up in the api docs together. Dana Walker Associate Software Engineer Red Hat On Fri, Mar 1, 2019 at 2:00 PM Justin Sherrill wrote: > To me this mak

Re: [Pulp-dev] Unified interface for plugin actions

To me this makes a lot of sense, allows for plugin flexibility, and is more consistent across plugins. I feel like this will make differences between plugins more understandable by reading the api docs, rather than scanning the README's of the respective plugin and trying to work out what is d

[Pulp-dev] Unified interface for plugin actions

Now that we have a handful of plugins that have somewhat different workflows, surprising user-facing differences in the interface for plugin-related actions are becoming apparent. Example: Publish File: Create a publisher v3/publishers/file/1/publish/ repository=$REPO Ansib