A call sequence diagram of uploading Ansible Collection content from Mazer to Galaxy and stored in Pulp

collection_upload.dot

@startuml
autonumber

title Collection Upload and then Fetch

participant Mazer

box "galaxy.example.com"
participant Nginx
participant "Galaxy's WSGI Process"
participant "Pulp's Webserver"
end box


' Push Content to Galaxy
Mazer [#red]-> Nginx : POST https://galaxy.ansible.com/api/v1/namespace/:id/collection/

' Route the request to Galaxy's WSGI app where authentication is performed
"Nginx" [#green]-> "Galaxy's WSGI Process" : POST /api/v1/namespace/:id/collection/

' Upload to Pulp's API
"Galaxy's WSGI Process" [#cyan]-> "Pulp's Webserver" : POST pulp.internal/pulp_galaxy/api/v1/
"Galaxy's WSGI Process" <-[#cyan] "Pulp's Webserver" : 200 OK with link to /pulp/api/v3/tasks/:uuid/

' Monitor the Upload Progress
"Galaxy's WSGI Process" [#cyan]-> "Pulp's Webserver" : GET pulp.internal/pulp/api/v3/tasks/:uuid/
"Galaxy's WSGI Process" <-[#cyan] "Pulp's Webserver" : 200 OK with status info. Eventually responding with 'complete'

' Notify Mazer
"Nginx" <-[#green] "Galaxy's WSGI Process" : 200 OK
Mazer <-[#red] Nginx : 200 OK

legend right
  (Red) -> HTTP(S) calls from and responses to Mazer
  (Cyan) -> WSGI Call/Response in Galaxy's Webserver
  (Green) -> Calls to, response from Pulp
endlegend
@enduml