Allow actions with custom URLs to use parameters from parent resource

[alexkreidler]

I have the following API Blueprint:

## Run Information [/processors/{id}/runs/{runID}]
Provides information about all the Runs on a given processor.

+ Parameters
    + id (string) - The processor ID
    + runID (string) - The run ID


### Retrieve One Run [GET]
+ Response 200 (application/json)
    + Attributes (Run)


### Configure [POST /processors/{id}/runs/{runID}/configure]
+ Response 200 (application/json)
    + Attributes (Run)

I want the Parameters from my "Run Information" ResourceGroup to cascade down to my Configure action, but instead, I get this:

So I need to add the + Parameters section to the Action itself, causing duplication.

Additionally, if we were able to use relative URIs (#451), then I wouldn't even have to write /processors/{id}/runs/{runID}/configure, I'd just write ./configure. Once this Parameters cascade issue is fixed, then it'd be super easy to add new actions without duplicating anything.

[kylef]

I think this is a bug in Aglio, you may want to file a bug with that software instead.

Other reference documentation renderers offer this: