api keys missing usage plans?

I understand how to require an api key, but I don't see how to get the AWS::ApiGateway::ApiKey, AWS::ApiGateway::UsagePlan & AWS::ApiGateway::UsagePlanKey generated into the sam.json (I'm targeting a CloudFormation deployment). Isn't requiring an api key kind of pointless if one can't be configured? I realize I can use the awscli to create these resources post-CloudFormation, but that kind of defeats the purpose of using CloudFormation in the first place. Am I missing something?

Start by inspecting Chalice's CloudFormation generation for sam.json and the handling of AWS::ApiGateway::ApiKey, AWS::ApiGateway::UsagePlan, and AWS::ApiGateway::UsagePlanKey. Determine whether these resources are supported and document the expected CloudFormation behavior or the implementation scope needed.

Written by the indexing model from the issue text.