How to solve an existential issue serverless".ts" vs ".yml"

Hi guys,

Hi guys,
I just can’t fix a problem that exist because I did generate my serverless app by template “aws-nodejs-typescript”. The issue basically happens because this template generates serverless.ts that can’t be selected on CI/CD obviously because it’s not right extension.

My nightmare begins when I try to transcode my .ts functions schema right there on serverless.ts to serverless.yml.

YES I think make sense keep it on .yml file not .ts.

So the question here is how do I keep the smart schema generated by .ts and make it happens on .yml.

i.e:
1 - On serverless.ts generated by template we see:

import HttpPostProduct from '@functions/product/httpPost';
import HttpPutProduct from '@functions/product/httpPut';
import HttpScanProduct from '@functions/product/httpScan';
import HttpGetProduct from '@functions/product/httpGet';
import HttpDeleteProduct from '@functions/product/httpDelete';
...

functions: { 
    HttpPostProduct,
    HttpPutProduct,
    HttpScanProduct,
    HttpGetProduct
    HttpDeleteProduct,
  },

2 - The same on serverless.yml we’ll see

functions:
  create:
    handler: functions/product/httpPost
    events:
      - http:
          path: product
          method: post
  update:
    handler: functions/product/httpPut
    events:
      - http:
          path: product/{id}
          method: put

So, I just want to keep the option 1 on .yml schema but my sls deploy doesn’t work like that

I’ll appreciate any help.
Thanks a lot