You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create type v1 or v2: v2
App kind (linux/windows, code/container): linux
If code, which runtime stack: python/node
Create template: Queue trigger, ServiceBus Queue trigger, ServiceBus Topic trigger, Blob trigger, EventHub trigger, CosmosDB trigger, EventGrid trigger
Issues:
The connection string properties for any resource type have a default string (ex. CosmosDbConnectionString). This string is not a valid option (as in it is not one of the user's database/event hub/service bus etc connection strings) and it prevents us from picking a value from the list we get based on the resource type. In template v1, the default value for resource types is undefined and it works correctly.
This issue reproduces in production in both the new/old function create experience.
The text was updated successfully, but these errors were encountered:
Create type v1 or v2: v2
App kind (linux/windows, code/container): linux
If code, which runtime stack: python/node
Create template: Queue trigger, ServiceBus Queue trigger, ServiceBus Topic trigger, Blob trigger, EventHub trigger, CosmosDB trigger, EventGrid trigger
Issues:
The connection string properties for any resource type have a default string (ex. CosmosDbConnectionString). This string is not a valid option (as in it is not one of the user's database/event hub/service bus etc connection strings) and it prevents us from picking a value from the list we get based on the resource type. In template v1, the default value for resource types is undefined and it works correctly.
This issue reproduces in production in both the new/old function create experience.
The text was updated successfully, but these errors were encountered: