Generator assumes namespace of non-essential generated files.

[jdnurmi]

Using the highly supported case of writing my own api-2.json to "execute-api:Invoke" functions with signing through the API gateway, invoking 'private/model/cli/gen-api' against my custom JSON and using the generated code mostly works (yay!)

Nits:

• examples_test.go and */interface.go assume the "github.com/aws/aws-sdk-go" namespace - which is reasonable as a default, but it'd be great to be able to make them configurable/relative (it breaks go build <custom-namespace>/... if those generated files are in the path). Removing them fixes the issue (and builds with the generated code succeed just fine, so it's mostly cosmetic.
• Schema failures ( undefined "shapes", etc) could be [better] reported

For the next guy down this road:

metadata:
"endpointPrefix":"<your-endpoint-id>.execute-api",
"signingName": "execute-api",

and expect to spend a lot of time w/ the api gateway writing mappings for reasons that aren't wholly clear...

set($inputRoot = $input.path('$'))

{
"stage" : "$context.stage",
"request-id" : "$context.requestId",
"api-id" : "$context.apiId",
"resource-path" : "$context.resourcePath",
"resource-id" : "$context.resourceId",
"http-method" : "$context.httpMethod",
"source-ip" : "$context.identity.sourceIp",
"user-agent" : "$context.identity.userAgent",
"account-id" : "$context.identity.accountId",
"api-key" : "$context.identity.apiKey",
"caller" : "$context.identity.caller",
"user" : "$context.identity.user",
"user-arn" : "$context.identity.userArn",
"inputRoot": "$inputRoot"
}

Might get you started.

[jasdel]

HI @jdnurmi thanks for contacting us about this. The generator code is something that would be cool to expose outside of the SDK and make it generic for general use. At the moment its design and usage is very specific to the SDK.

Expanding the generator code logic outside of the SDK would be a cool feature and would allow people do generate some interesting logic for their applications using the SDK.

Marking this as an enhancement so we can track the progress of this enhancement.

[jasdel]

@jdnurmi I've committed a change which will allow you to specify the base import path for service clients. The client still expects to live in it's own folder/package but this will allow you to generate service clients based on your API Gateway APIs in your own package paths.