Skip to content

Fix documentation for azure blob trigger #11874

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: v3
Choose a base branch
from

Conversation

mohsin-moideen
Copy link

Trying to deploy serverless app by following the existing documentation throws "Error: Binding nameTrigger not supported". Indentation mistake in the documentation is for the name parameter.

Closes: #{ISSUE_NUMBER}

Trying to deploy serverless app by following the existing documentation throws  "Error: Binding  nameTrigger not supported".
Indentation mistake in the documentation is for the name parameter.
Copy link
Contributor

@medikoo medikoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mohsin-moideen thanks for the fix. Still, I believe all items under event type should have indentation fixed (not just name). Can you update it?

@mohsin-moideen
Copy link
Author

the parameters 'path' and 'connections' do not get picked up when indentation is on the same level as 'name'.
could be an issue with the parser?

@medikoo
Copy link
Contributor

medikoo commented Mar 30, 2023

@mohsin-moideen convention in the Framework is that all event properties are nested like that.

Azure plugin might author, possibly pursued some other attempt. As I check the other examples, properties are nested but in x-azure-settings properties as here: https://github.com/serverless/examples/blob/v3/azure-node-telegram-bot/serverless.yml#L49-L58

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants