title: AWS endpoint not being deployed to stages when using Serverless
body: <p>I'm trying to add a new endpoint to an existing service, and while it shows on the API Gateway Resources page, it's not showing on the Stages page. Hitting the endpoint returns the header <code>x-amzn-ErrorType</code> as <code>IncompleteSignatureException</code> and an error that includes the JWT token and <code>not a valid key=value pair (missing equal-sign) in Authorization header</code>.</p>
  <p>Our setup uses a swagger file to define the endpoints, and uses <code>x-amazon-apigateway-integration</code> to link the endpoint to the lambda function. On first deployment of the new endpoint, we had some problems as this integration was setup wrong, but has since been corrected to match the others (suspect this is where the problem lies).</p>
  <p>I've tried making sure that the new endpoint config matches that of other working endpoints; I've removed the endpoint, redeployed, added it back and redeployed; I've renamed the lambda. None of these have worked.</p>
  <p>The swagger file looks like:</p>
  <pre><code>  /companies/{id}/info:
      get:
        consumes:
          - application/json
        produces:
          - application/json
        responses:
          &quot;200&quot;:
            description: successful operation
            headers:
              Access-Control-Allow-Origin:
                type: string
        x-amazon-apigateway-integration:
          uri:
            Fn::Join:
              - &quot;&quot;
              - - Fn::Join:
                    - &quot;&quot;
                    - - &quot;arn:aws:apigateway:&quot;
                      - Ref: AWS::Region
                      - &quot;:lambda:path/2015-03-31/functions/&quot;
                - Fn::GetAtt:
                    - GetCompanyInfoLambdaFunction
                    - Arn
                - &quot;/invocations&quot;
          httpMethod: POST
          type: aws_proxy
      post:
        #... this method works fine with same config but different lambda
  </code></pre>
  <p>Any ideas as to how to fix this? Thanks</p>