cosmosDB bindings: Error: Binding direction/name/databaseName/collectionName not supported

[blomm]

This is a Bug Report

Description

• What went wrong? : when running sls offline or sls deploy, this error pops up
• What did you expect should have happened? publish to azure with a function that allows me to read/write with cosmosDB
• What was the config you used? (pretty much straight from the docs)

functions:
  sampleQuery:
    handler: src/handlers/sample.query
    events:
      - http: true
        methods:
          - POST
        authLevel: anonymous
      - cosmosDB:
        direction: out
        name: record # name of input parameter in function signature
        databaseName: sampleDB
        collectionName: sampleCollection
        connectionStringSetting: COSMOS_DB_CONNECTION # name of appsetting with the connection string
        createIfNotExists: true # A boolean value to indicate whether the collection is created when it doesn't exist.

• What stacktrace or error message from your provider did you see? Error: Binding direction not supported at Function. (/Users/michaelblom/development/nanook/reporting-config-api/node_modules/serverless-azure-functions/lib/shared/utils.js:99:39)

Similar or dependent issues:

• I thought it a bit strange that the error message has 2 spaces between Binding and direction, so i've play around with the indentation a bit, but that didn't fix anything.

Additional Data

Your Environment Information --------------------------- Operating System: darwin Node Version: 10.16.0 Framework Version: 2.8.0 Plugin Version: 4.1.1 SDK Version: 2.3.2 Components Version: 3.2.7

• Provider Error messages: Error: Binding direction not supported at Function. (/Users/michaelblom/development/nanook/reporting-config-api/node_modules/serverless-azure-functions/lib/shared/utils.js:99:39)

[blomm]

It's essentially not liking any bindings under cosmosDB, am I missing a needed plugin? I've got serverless-azure-functions installed and I mention it in the plugins section of the serverless.yml file

[blomm]

I added some extra logging:

if (index < 0) {
                                console.log("acceptable binding types: " + JSON.stringify(bindingTypes))
                                throw new Error("Binding  " + bindingType + " not supported");
                            }

what it printed out was this: ["timerTrigger","eventHubTrigger","eventHub","queue","queueTrigger","blob","blob","blobTrigger","apiHubFile","apiHubFile","apiHubFileTrigger","apiHubTable","apiHubTable","httpTrigger","http","serviceBusTrigger","serviceBus","manualTrigger","table","table","cosmosDB","cosmosDB","cosmosDBTrigger","mobileTable","mobileTable","notificationHub","sendGrid","twilioSms","bot","bot"]

[blomm]

when I don't include any properties under cosmosDB, it says: Error: Required property connectionStringSetting is missing for binding:cosmosDB When I add connectionStringSetting (or anything under cosmosDB) it says: Error: Binding connectionStringSetting not supported

[jis260]

I have been having similar issues with the sendGrid binding. I also just tried the cosmosDB binding and I found that I need to use "x-azure-settings:" like:

- cosmosDB:
  x-azure-settings:
    direction: out
    name: record # name of input parameter in function signature
    databaseName: databaseName
    collectionName: collectionName
    connectionStringSetting: COSMOS_DB_CONNECTION # name of appsetting with the connection string
    createIfNotExists: false # A boolean value to indicate whether the collection is created when it doesn't exist.

If I look at the Azure function "function.json" it has:

{
      "type": "cosmosDB",
      "direction": "out",
      "name": "record",
      "databaseName": "databaseName",
      "collectionName": "collectionName",
      "createIfNotExists": false,
      "connectionStringSetting": "COSMOS_DB_CONNECTION"
 } 

I also found that if you don't have another output binding specified then the "name" property gets ignored and is set to "$return". So I set it like:

    events:
      - http: true
        methods:
          - POST
        authLevel: function
      - http:
        x-azure-settings:
          direction: out
      - cosmosDB:
        x-azure-settings:
          direction: out
          name: doc
          databaseName: databaseName
          collectionName: collectionName
          connectionStringSetting: COSMOS_DB_CONNECTION # name of appsetting with the connection string
          createIfNotExists: false # A boolean value to indicate whether the collection is created when it doesn't exist.  

In the function.json it displays as:

   {
      "type": "httpTrigger",
      "direction": "in",
      "name": "req",
      "authLevel": "function",
      "methods": [
        "POST"
      ]
    },
    {
      "type": "http",
      "direction": "out",
      "name": "$return"
    },
    {
      "type": "cosmosDB",
      "direction": "out",
      "name": "doc",
      "databaseName": "databaseName",
      "collectionName": "collectionName",
      "createIfNotExists": false,
      "connectionStringSetting": "COSMOS_DB_CONNECTION"
    }

For sendGrid this does not seem to work. Unfortunately, I have been unable to get the output binding working correctly. Whenever, the cosmosDB binding is included and I try to call the Azure function it gives a 404 not found error.

[jis260]

I should add that: Framework Core: 1.73.0 Plugin: 3.6.13 SDK: 2.3.1 Components: 2.30.15

[jis260]

If I try the same approach with: Operating System: linux Node Version: 12.18.1 Framework Version: 2.9.0 (standalone) Plugin Version: 4.1.1 SDK Version: 2.3.2 Components Version: 3.2.7

Error: Binding not supported If I remove x-azure-settings: then I get this error: Error: Required property createIfNotExists is missing for binding:cosmosDB

[blomm]

For me, it doesn't matter what binding I put under cosmosdb, I get "Error: Binding not supported"

[ianrandell-sh]

try setting - cosmosDB:

to - cosmosDB: true

I've had similar issue with serviceBus binding and been debugging the transpiled js For ref my yaml had to look like this:

functions:
  myFunc:
    handler: myFunc.Run
    events:
      - serviceBus: true  #<--- NEED TRUE HERE
        name: message
        queueName: myQueue
        accessRights: manage
        connection: SERVICE_BUS_CONNECTION

The x-azure-settings is irrelevant for the latest version of the plugin.

[blomm]

Interestingly, adding "true" means that it only complains about one property, "connectionStringSetting", rather than complaining about the first one on the list. Error: connectionStringSetting not supported and when I remove it: Error: Required property connectionStringSetting is missing for binding:cosmosDB

I was only trying with the x-azure-settings because I saw in the code that although it was legacy it was still supported.

[ianrandell-sh]

Possibly "connectionStringSetting" should be "connection"

Edit: looks like it should be "connectionStringSetting"

[ngjm]

try setting - cosmosDB:

to - cosmosDB: true

I've had similar issue with serviceBus binding and been debugging the transpiled js For ref my yaml had to look like this:

functions:
  myFunc:
    handler: myFunc.Run
    events:
      - serviceBus: true  #<--- NEED TRUE HERE
        name: message
        queueName: myQueue
        accessRights: manage
        connection: SERVICE_BUS_CONNECTION

The x-azure-settings is irrelevant for the latest version of the plugin.

@ianrandell-sh Thank you for this. This fixed an issue the issue I was seeing for the eventHub trigger.