My account has access to multiple tenants. I would need to specify which one so that it can find the subscriptions.

Currently it finds no subscription from any of my tenants.

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.

Merge this pull request

Since we would no longer ship whole modules with our extension

Here's the repo with the JSON schema for 1st party events:
https://github.com/Azure/azure-rest-api-specs/tree/master/specification/eventgrid/data-plane

This is all about being able to debug your event grid subscriptions

When creating an Event Grid Subscription, we only let people specify a webhook for the subscriber endpoint. However, it might be easier for people to use a storage queue:
https://docs.microsoft.com/en-us/azure/event-grid/custom-event-to-queue-storage

1. Create topic1
2. msg: Successfully created topic "topic1".
3. Create topic1
4. msg: Successfully created topic "topic1".
5. Node in treeview closes to not show any topic

The error detection for events are a bit vague today. We could probably do some JSON parsing to make sure that the necessary properties exist before an event is sent out.

Repro steps:

1. Generate a Mock Event
2. Change eventSchema to an incorrect property (ie eventsdfasdfsSchema)
3. Try to send to preview

Action: azureEventGridSubscription.sendEvents
Error type: TypeError
Error Message: Cannot convert undefined or null to object

Version: 0.1.0
OS: win32

Hello 👋 I'm from the VS Code team.

Recently, we have been exploring a security feature we refer to as Workspace Trust. This feature is intended to centralize and unify a security conscious decision required by a variety of VS Code features. With workspace trust, the user will be able to declare whether or not they trust the folder that is opened in VS Code before these features are executed.

Why you should care

Your extension is incredibly popular with VS Code users! We want to make sure that those users have a delightful experience with workspace trust and that includes extension authors deciding how much of their extension is supported in an untrusted workspace.

Workspace Trust experience

You can enable the feature with the following setting security.workspace.trust.enabled. Once enabled, you will see the following dialog when opening folders in VS Code.

This dialog is important for allowing the user to make a decision early and understand the impact of their decision. Once you understand the feature, you may want to customize when to display the dialog using the setting security.workspace.trust.startupPrompt.

You can follow the development of Workspace Trust and provide feedback in issue #106488.

Workspace trust API

First off, all of what I am about to say can be found in issue #120251. That issue will include discussion of the feature and any updates to the feature.

The Workspace Trust extension API is now in stable. This allowed us to release the first cut of our guide for onboarding your extension to Workspace Trust. The API is small, so here is a quick look.

You can declare your extension to provide complete, partial or no support in untrusted workspaces using the untrustedWorkspaces capability in package.json.

The following example declares that the extension is supported completely in untrusted workspaces. In this case, the extension is enabled in untrusted workspaces.

"capabilities": {
  "untrustedWorkspaces": {
    "supported": true
  }
}

The next example declares that the extension is not supported in untrusted workspaces. In this case, the extension is disabled in untrusted workspaces.

"capabilities": {
  "untrustedWorkspaces": {
    "supported": false
  }
}

The third option is to declared limited support. There are three tools provided to you when you select the limited option.

First, if you have a setting that can be configured in the workspace but requires the workspace to be trusted in order to apply the workspace value, then you can include the setting using restrictedConfigurations array property in untrustedWorkspaces object. Doing so, VS Code will ignore the workspace value of these restricted settings when your extension reads these settings values using the VS Code Workspace Configuration API.

The following example declares the settings that are restricted in untrusted workspaces.

"capabilities": {
  "untrustedWorkspaces": {
    "supported": "limited",
    "restrictedConfigurations": [
      "markdown.styles"
    ]
  }
}

Next, you can also check and listen if the current workspace is trusted or not programmatically using the following API:

export namespace workspace {
  /**
   * When true, the user has explicitly trusted the contents of the workspace.
   */
  export const isTrusted: boolean;
  /**
   * Event that fires when the current workspace has been trusted.
   */
  export const onDidGrantWorkspaceTrust: Event<void>;
}

Lastly, you can hide commands or views declaratively with the isWorkspaceTrusted context key in your when clauses.

A far more detailed guide on how to onboard which will be updated as we receive feedback can be found in issue #120251.

Rollout plan

Workspace Trust will remain disabled for the month of May, but we are planning on enabling this by default in the future. To prepare for that day, we would love for you to try it out and provide feedback.

We'd love your feedback

Since this issue was created in an automated fashion, we won't be monitoring the responses in this issue (our notifications would explode!). Instead we ask you to drop questions, and feedback in issue #120251 as we've mentioned above.

We're excited to see what you do with workspace trust!

https://github.com/Azure/azure-sdk-for-js/blob/master/documentation/Migration.md

• Issue Type: Performance
• Extension Name: vscode-azureeventgrid
• Extension Version: 0.1.1
• OS Version: Windows_NT x64 10.0.18362
• VSCode version: 1.38.1

⚠️ Make sure to attach this file from your home-directory:
⚠️C:\Users\rajkr\ms-azuretools.vscode-azureeventgrid-unresponsive.cpuprofile.txt

Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

WORKAROUND: Please update to vscode 1.31.1 or higher (current is 1.33) or else install the previous version of the extension. A fix will be available in the next week or two.

Use Help -> Check for Updates...
or download from here: https://code.visualstudio.com/updates/v1_31

microsoft/vscode-azuretools#200

If you create an event subscription with the same name, location, and type, it will say that it was successfully created, but cause the node to temporarily break.

Repro steps:

1. Create a topic
2. Try to create another topic with the same name

Action: azureEventGridTopic.createTopic
Error type: ResourceConflict
Error Message: Topic with name eventtopic01 already exists. Choose a different topic name.

Version: 0.1.0
OS: win32

What I am trying to achive is to write an Azure function that does something when a file is uploaded into a blob container. I would like to test this locally with a blob storage created with Azurite and mock events sent by the Azure Event Grid extension in VS Code.

The function would look like this:

[FunctionName("BlobstorageMyContainerNotifications")]
public async Task RunMyContainerNotificationsAsync(
    [BlobTrigger("mycontainer/{blobName}", Source = BlobTriggerSource.EventGrid, Connection = "AzureWebJobsStorage")] Stream blobStream,
    string blobName,
    ILogger log)
    {
        await DoSomeStuff("mycontainer", blobName, log);
    }

I have created an event generator with the command Azure Event Grid Subscription: Create Mock Event Generator, set the event type to Storage and set the Subscriber Endpoint to http://localhost:7071/runtime/webhooks/blobs?functionName=BlobstorageMyContainerNotifications.

Then I run my Azure function app locally and click the Send Events button.
The App is then prints one of the following error messages:

When this happens, the app does not crash.

[2022-11-02T10:33:35.498Z] Executing HTTP request: {
[2022-11-02T10:33:35.499Z]   requestId: "a5d9f7c2-da9a-403e-8d09-7d42eb55777a",
[2022-11-02T10:33:35.500Z]   method: "POST",
[2022-11-02T10:33:35.501Z]   userAgent: "(null)",
[2022-11-02T10:33:35.501Z]   uri: "/runtime/webhooks/blobs"
[2022-11-02T10:33:35.502Z] }
[2022-11-02T10:33:35.541Z] An unhandled host error has occurred.
[2022-11-02T10:33:35.542Z] Microsoft.Azure.WebJobs.Extensions.Storage.Blobs: Object reference not set to an instance of an object.
[2022-11-02T10:33:35.543Z] Executed HTTP request: {
[2022-11-02T10:33:35.543Z]   requestId: "a5d9f7c2-da9a-403e-8d09-7d42eb55777a",
[2022-11-02T10:33:35.544Z]   identities: "(WebJobsAuthLevel:Admin, WebJobsAuthLevel:Admin)",
[2022-11-02T10:33:35.544Z]   status: "500",
[2022-11-02T10:33:35.545Z]   duration: "45"
[2022-11-02T10:33:35.545Z] }

When this happens, the app does crash.

[2022-11-02T10:35:43.402Z] An unhandled exception has occurred. Host is shutting down.
[2022-11-02T10:35:43.402Z] Azure.Storage.Blobs: Service request failed.
[2022-11-02T10:35:43.403Z] Status: 400 (The specifed resource name contains invalid characters.)
[2022-11-02T10:35:43.404Z] ErrorCode: InvalidResourceName
[2022-11-02T10:35:43.404Z] 
[2022-11-02T10:35:43.405Z] Headers:
[2022-11-02T10:35:43.405Z] Server: Azurite-Blob/3.20.1
[2022-11-02T10:35:43.406Z] x-ms-error-code: InvalidResourceName
[2022-11-02T10:35:43.407Z] x-ms-request-id: 9e0b114d-c01e-46ce-914d-4d5f0cc61784
[2022-11-02T10:35:43.407Z] Date: Wed, 02 Nov 2022 10:35:43 GMT
[2022-11-02T10:35:43.408Z] Connection: keep-alive
[2022-11-02T10:35:43.408Z] Keep-Alive: REDACTED
[2022-11-02T10:35:43.409Z] .

Is it possible to do something like this with this extension? Or am I missing something?

When creating event subscription

👋 Hi there, Martin here, from the VS Code team.

Recently we've announced the Remote Repository feature that lets you browse and edit files and folders directly on GitHub.

Open Remote Repository... opens VSCode on a folder or workspace located on a virtual file system. We call this a virtual workspace. We observed that not all extension support this well, either because they can not, or they haven't thought about it.

It would be fantastic if you could test whether your extension can handle virtual workspaces:

Check out the Virtual Workspaces Extension Author Guide on how to do that.

When done, set the new virtualWorkspaces capability in your 'package.json'.

{
  "capabilities": {
    "virtualWorkspaces": true | false
  }
}

• Use "virtualWorkspaces": true if your extension is prepared for virtual workspaces
• Use "virtualWorkspaces": false if your extension should be disabled when a virtual workspace is opened

For questions and comments please use the Virtual Workspaces Tracking Issue.

Thanks for the support and the great work! ❤️

As I'm not a user of event grid, I'm unsure how helpful this may be, but there isn't an easy way to discern what type of event subscription I'm generating mock events for.

• Issue Type: Performance
• Extension Name: vscode-azureeventgrid
• Extension Version: 0.1.1
• OS Version: Windows_NT x64 10.0.18363
• VSCode version: 1.44.2

⚠️ Make sure to attach this file from your home-directory:
⚠️C:\Users\user\ms-azuretools.vscode-azureeventgrid-unresponsive.cpuprofile.txt

Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

This extension uses version 0.0.18 of vscode-extension-telemtetry module.

The latest version of vscode-extension-telemtetry module (0.1.0) uses the latest version of applicationinsights module (1.0.6) which has the fix to prevent unnecessary patching of the require and other 3rd party modules.

For more details, please see microsoft/vscode-extension-telemetry#16

Most of the 'getting started' docs recommend using hookbin to start off, but I've never gotten that to work:
https://docs.microsoft.com/azure/storage/blobs/storage-blob-event-quickstart?toc=%2fazure%2fevent-grid%2ftoc.json

I have better luck just using an Azure Function, but that's more complicated (especially if users aren't familiar with functions). Here's the docs on that: https://docs.microsoft.com/azure/azure-functions/functions-bindings-event-grid

Some property reccommendations for properties.

Repro steps:

1. new eventgrid subscription
2. press ENTER for subscriber endpoint
3. error
   EXPECTED: validation

Action: azureEventGridSubscription.createEventSubscription
Error type: InvalidRequest
Error Message: Invalid event subscription request: endpoint.

Version: 0.1.0-alpha
OS: win32