Unsupported configuration format

Serverless Framework
,
1

Hi I’m trying to shift from serverless v2.x to v3 but after moving I’m getting this warning/error which I’ll like to learn the root cause of:

Error:
Configuration error at 'constructs.sms-queue': unsupported configuration forma

Here’s my configuration file

service: aws-node-sqs-sms-notification-worker

frameworkVersion: "3"

useDotenv: true
configValidationMode: error

provider:
  name: aws
  runtime: nodejs16.x
  stage: ${opt:stage, 'dev'}
  region: ${file(serverless.env.yml):${self:custom.stage}.REGION}
  timeout: 900
  tracing:
    lambda: true
  vpc:
    securityGroupIds:
      - sg-081e8e489a3c68214
    subnetIds:
      - subnet-05d81d57cb97eaa1f
      - subnet-0c8d39aa74e13666d

constructs:
  sms-queue:
    type: queue
    worker:
      handler: src/worker.handler
      environment:
        MONGO_URI: ${file(config.json):kDatabasePath}
        kEnvironment: ${file(serverless.env.yml):${self:custom.stage}.kEnvironment}
        kSMSApiKey: ${file(config.json):kSMSApiKey}
        kSMSSenderId: ${file(config.json):kSMSSenderId}
        kOTPServiceProvider: ${file(config.json):kOTPServiceProvider}
        kGupShupUserName: ${file(config.json):kGupShupUserName}
        kGupShupPassword: ${file(config.json):kGupShupPassword}
        kAndroidKeyStoreHash: ${file(config.json):kAndroidKeyStoreHash}
        kClicktellApiKey: ${file(config.json):kClicktellApiKey}
        ktestPhoneNumbers: ${file(config.json):ktestPhoneNumbers}
    environment:
      QUEUE_URL: ${construct:sms-queue.queueUrl}

#functions:
#  producer:
#    handler: src/publisher.handler
#    events:
#      - http:
#          method: post
#          path: produce
#    environment:
#      QUEUE_URL: ${construct:sms-queue.queueUrl}

custom:
  stage: "${opt:stage, self:provider.stage}"
  webpack:
    webpackConfig: "webpack.config.js"
    packager: "npm"
    includeModules: true

plugins:
  - serverless-lift
  - serverless-webpack
  - serverless-offline
2 Likes
2

Did you find a solution for this? I’m currently seeing the same error.