The problem discussed in WFCORE-6981 goes beyond the reply-properties I focused on there. The request properties are also wrong, with the basic issue also applying to 'upload-deployment'xxx' ops where xxx != 'url'. They all use an AD derived from a 'content' attribute meant for ops where alternative parameters are allowed. But for these ops, alternatives are not allowed; the OSHs only know how to handle a single kind of content.