Skip to main content

EVENT GRID

Pushing messages to system topics

We do this when the subscribers are azure resources. 

Create an azure function that gets triggered when txt files are uploaded to a blob container named container1.

Steps:

1. Create a storage account






2. Create a 2 containers , container1 and container2.


3. Create an azure function

Create a function app and create an event grid triggered function in it.





4. Create an event subscription for the storage account



Create filtering rules in the subscription such that only specific events trigger the azure function. When creating the new subscription we need to create a filter such that only txt files uploaded to container1 trigger the event which in turn would invoke the azure function.



When filtering message based on the container prepend /blobServices/default/containers/{containername}

5. Upload blobs to container1 and 2 of different file formats and notice that only txt file uploaded to container1 trigger the function.






We can do the same thing by going to the portal and creating a event grid system topic and then adding a subscription to it. The easier way is to go to the storage account and add an event subscription under the events menu.

Sending Messages to custom topics

 class Program
    {
        
        async static Task Main(string[] args)
        {
            string endpoint = "";
            string key = "";
            string topicHostName = new Uri(endpoint).Host;

            EventGridEvent acct = new EventGridEvent(
                id: Guid.NewGuid().ToString(), 
                subject: "New Account", 
                data: new {Message = "hi"}, 
                eventType: "NewAccountCreated", 
                eventTime: DateTime.Now, 
                dataVersion: "1.0");
            
            TopicCredentials credentials = new TopicCredentials(key);

            EventGridClient client = new EventGridClient(credentials);

            await client.PublishEventsAsync(topicHostName, new EventGridEvent[] { acct });
        }
    }

<ItemGroup>
    <PackageReference Include="Microsoft.Azure.EventGrid" Version="" />
  </ItemGroup>

Receiver

using System;
using System.Collections.Generic;
using System.Linq;
using System.Threading.Tasks;
using System.IO;
using Microsoft.AspNetCore.Mvc;
using Microsoft.Extensions.Logging;

using Microsoft.Azure.EventGrid.Models;

using Newtonsoft.Json;
using Newtonsoft.Json.Linq;


namespace SendNotification.Controllers
{
    [ApiController]
    [Route("[controller]")]
    public class SendNotificationController : ControllerBase
    {
        // from example at: https://github.com/Azure-Samples/azure-event-grid-viewer/blob/main/viewer/Controllers/UpdatesController.cs
        private bool EventTypeSubcriptionValidation
            => HttpContext.Request.Headers["aeg-event-type"].FirstOrDefault() ==
               "SubscriptionValidation";

        private bool EventTypeNotification
            => HttpContext.Request.Headers["aeg-event-type"].FirstOrDefault() ==
               "Notification";

        private readonly ILogger<SendNotificationController> _logger;

        public SendNotificationController(ILogger<SendNotificationController> logger)
        {
            _logger = logger;
        }

        [HttpPost]
        public async Task<IActionResult> Post()
        {
            using (var requestStream = new StreamReader(Request.Body))
            {
                var bodyJson = await requestStream.ReadToEndAsync();

                var events = JsonConvert.DeserializeObject<List<EventGridEvent>>(bodyJson);
                                            
                if (EventTypeSubcriptionValidation)
                {                
                    var subValidationEventData = 
                        ((JObject)events.First().Data).ToObject<SubscriptionValidationEventData>();
                                        
                    return new OkObjectResult(
                        new SubscriptionValidationResponse(subValidationEventData.ValidationCode)
                    );
                }
                else if (EventTypeNotification) 
                {                
                    var notificationEvent = events.First();

                    _logger.LogInformation(notificationEvent.Subject);

                    return new OkResult();
                }
            }

            return new BadRequestResult();
        }
    }
}




Comments

Post a Comment

Popular posts from this blog

Azure AD Authentication And Authorization

ROLE BASED AUTHORIZATION Step1:   Setup  API. 1. Create an app registration and create an app role. Make sure that the app role is assigned to user and applications. We add it to both user groups and applications as this role can be then assigned to both users and applications. Scopes can only be assigned to apps. Now we can have only users with this role access our application. This app role behind the scenes adds an approles section to the manifest.json. We can directly add it to the manifest file also. Step 2:  Setup an app registration for the UI/ WEB App. . We will grant this app the read role created in the API app (shown above). Go to Azure AD and select the UI app registration. When we register an application 2 elements get created. 1. App registration  2. Enterprise Application -- service principal that get created for the app Adding roles to applications Go to the App registration => API Persmissions => Add a Permission => My API's The My Api's sec...
Post a Comment
Read more

Function APP and KV integration

 Create a function App and enable system assigned identity Create  a Keyvault and add a secret (Name in my case) Configure Access policies for the function app in keyvault Create an  access policy in Key Vault   for the application identity you created earlier. Enable the "Get" secret permission on this policy. Do not configure the "authorized application" or   applicationId   settings, as this is not compatible with a managed identity. https://docs.microsoft.com/en-us/azure/app-service/app-service-key-vault-references Key Vault references currently only support system-assigned managed identities. User-assigned identities cannot be used. We are granting our function app permissions to get and list all the secrets in this keyvault. Add Key Vault secrets reference in the Function App configuration Go to the keyvault and click on the secret we just created. Copy the secret identifier. We need to add this value to the function app configuration.  @Microsof...
Post a Comment
Read more

AZ-500 AppService Inside VNet

The intent is to create an appservice that is available inside a VNET. So we will create a vnet and put an appservice inside it. This Vnet will have 2 subnets. One that has the appservice and another one that will have a VM.. We need to make sure that this Appservice can be accessed only inside the VM (inside the same VNET)  1. Create a Vnet Total Address space is 256.. We split into 2 subnets 2. Create an Appservice in standard or above tier as the lower tiers dont support networking.  and select the Vnet and select the sub2 subnet 3. Create a Virtual Machine inside sub1. 4. Go to Appservices and onto the networking tab and select Access Restrictions Create a rule and select VNET and subnet that we created earlier. We can also specify IP Address. Then this appservice can be accessed by the specified IP's only. So this appservice can only be accessed within subnet 1. Which is where we have deployed the VM.. From Internet Inside VM (Subnet 1)
Post a Comment
Read more