Skip to content
This repository has been archived by the owner on Feb 15, 2024. It is now read-only.

Azure/aml-function

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

8 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Deploy to Azure

function_app

This repository contains an Azure Function app which contains an Http Trigger function. The function can send github repository dispatch event when triggered. It is modelled to send All type of Azure events when subscribed to the event grid of the workspace with the endpoint as the function url. This function-app once deployed the function can be registered to event grid either manually or using our GitHub Action.

Basic Requirements to use the function:

  1. Add personal access token in the application settings of the function app with the name PAT_TOKEN.

Basic Requirements to use the Deploy to Azure button (Mandatory):

  1. Subscription: You need to select a subscription plan in order to deploy to Azure. Get started today with a free Azure account!
  2. Resource Group: You can either select an existing resource group or create a new one.
  3. Pat Token: You need to provide the personal access token.
Other optional configurable parameters to use with Deploy to Azure button
  1. Function App Name: Name use as base-template to name the resources to be deployed in Azure (Default = fappDeploy).
  2. Function GitHub URL: The URL of GitHub (ending by .git)
  3. Function GitHub Branch: Name of the branch to use when deploying (Default = master).
  4. Function Folder: The name of folder containing the function code (Default = fappDeploy).
  5. Owner Name: Owner of this deployment, person to contact for question.
  6. Expire On: Just a text value (format: yyyy-MM-dd) that express when it is safe to delete these resources.

Events and its corresponding event types sent by the event-grid: Link

Azure App Configuration Events
  1.Microsoft.AppConfiguration.KeyValueModified: appconfiguration-keyvaluemodified
  2.Microsoft.AppConfiguration.KeyValueDeleted: appconfiguration-keyvaluedeleted
  
Azure App Service Events
  1.Microsoft.Web/sites.BackupOperationStarted: web/sites-backupoperationstarted
  2.Microsoft.Web/sites.BackupOperationCompleted: web/sites-backupoperationcompleted	
  3.Microsoft.Web/sites.BackupOperationFailed: web/sites-backupoperationfailed	
  4.Microsoft.Web/sites.RestoreOperationStarted: web/sites-restoreoperationstarted
  5.Microsoft.Web/sites.RestoreOperationCompleted: web/sites-restoreoperationcompleted
  6.Microsoft.Web/sites.RestoreOperationFailed: web/sites-restoreoperationfailed
  7.Microsoft.Web/sites.SlotSwapStarted: web/sites-slowswapstarted
  8.Microsoft.Web/sites.SlotSwapCompleted: web/sites-slowswapcompleted
  10.Microsoft.Web/sites.SlotSwapFailed: web/sites-slowswapfailed
  11.Microsoft.Web/sites.SlotSwapWithPreviewStarted: web/sites-slowswapwithpreviewstarted
  12.Microsoft.Web/sites.SlotSwapWithPreviewCancelled: web/sites-slowswapwithpreviewcancelled
  13.Microsoft.Web/sites.AppUpdated.Restarted: web/sites-appupdated-restarted
  14.Microsoft.Web/sites.AppUpdated.Stopped:  web/sites-appupdated-stopped
  15.Microsoft.Web/sites.AppUpdated.ChangedAppSettings:  web/sites-appupdated-changeappsettings
  16.Microsoft.Web/serverfarms.AppServicePlanUpdated: web/serverfarms-appserviceplanupdated
  
Azure Blob Storage Events
  1.Microsoft.Storage.BlobCreated: storage-blobcreated
  2.Microsoft.Storage.BlobDeleted: storage-blobdeleted
  
Azure Container Registry Events
  1.Microsoft.ContainerRegistry.ImagePushed: containerregistery-imagepushed
  2.Microsoft.ContainerRegistry.ImageDeleted: containerregistery-imagedeleted
  3.Microsoft.ContainerRegistry.ChartPushed: containerregistery-chartpushed
  4.Microsoft.ContainerRegistry.ChartDeleted: containerregistery-chartdeleted

Azure Event Hubs
  1.Microsoft.EventHub.CaptureFileCreated: eventhub-capturefilecreated

Azure IoT Hub
  1.Microsoft.Devices.DeviceCreated: devices-devicecreated
  2.Microsoft.Devices.DeviceDeleted: devices-devicedeleted
  3.Microsoft.Devices.DeviceConnected: devices-deviceconnected
  4.Microsoft.Devices.DeviceDisconnected: devices-devicedisconnected
  5.Microsoft.Devices.DeviceTelemetry: devices-devicetelementry

Azure Key Vault
  1.Microsoft.KeyVault.CertificateNewVersionCreated:  keyvault-certificatenewversioncreated, keyvault-certificatenearexpiry, 
  2.Microsoft.KeyVault.CertificateNearExpiry: keyvault-certificatenearexpiry
  3.Microsoft.KeyVault.CertificateExpired: keyvault-certificateexpired
  4.Microsoft.KeyVault.KeyNewVersionCreated: keyvault-keynewversioncreated
  5.Microsoft.KeyVault.KeyNearExpiry: keyvault-keynearexpiry
  6.Microsoft.KeyVault.KeyExpired: keyvault-keyexpired
  7.Microsoft.KeyVault.SecretNewVersionCreated: keyvault-secretnewversioncreated
  8.Microsoft.KeyVault.SecretNearExpiry: keyvault-secretnearexpiry
  9.Microsoft.KeyVault.SecretExpired: keyvault-secretexpired
  
Azure Machine Learning Events
  1.Microsoft.MachineLearningServices.ModelRegistered: machinelearningservices-modelregistered
  2.Microsoft.MachineLearningServices.ModelDeployed: machinelearningservices-modeldeployed
  3.Microsoft.MachineLearningServices.RunCompleted: machinelearningservices-runcompleted
  4.Microsoft.MachineLearningServices.DatasetDriftDetected: machinelearningservices-datadriftdetected
  5.Microsoft.MachineLearningServices.RunStatusChanged: machinelearningservices-runstatuschanged

Azure Maps Events
  1.Microsoft.Maps.GeofenceEntere: maps-geofenceentered 
  2.Microsoft.Maps.GeofenceExited: maps-geofenceexited
  3.Microsoft.Maps.GeofenceResult: maps-geofenceresult
  
Azure Media Services Events
  1.Microsoft.Media.JobStateChange: media-jobstatechange
  2.Microsoft.Media.JobScheduled: media-jobscheduled
  3.Microsoft.Media.JobProcessing: media-jobprocessing
  4.Microsoft.Media.JobCanceling: media-jobcanceling
  5.Microsoft.Media.JobFinished: media-jobfinished
  6.Microsoft.Media.JobCanceled: media-jobcanceled
  7.Microsoft.Media.JobErrore: media-joberrored
  8.Microsoft.Media.JobStateChange: media-joboutputstatechange
  9.Microsoft.Media.JobOutputScheduled: media-joboutputscheduled
  10.Microsoft.Media.JobOutputProcessing: media-joboutputprocessing
  11.Microsoft.Media.JobOutputCanceling: media-joboutputcanceling
  12.Microsoft.Media.JobOutputFinished: media-joboutputfinished
  13.Microsoft.Media.JobOutputCanceled: media-joboutputcanceled
  14.Microsoft.Media.JobOutputErrore: media-joboutputerrored

Azure Service Bus Events
  1.Microsoft.ServiceBus.ActiveMessagesAvailableWithNoListeners: servicebus-activemessageavailablewithnolisteners
  2.Microsoft.ServiceBus.DeadletterMessagesAvailableWithNoListener:  servicebus-deadlettermessagesavailablewithnolisteners
  
Azure SignalR Service Events
  1.Microsoft.SignalRService.ClientConnectionConnected: signalrservice-clientconnectionconnected
  2.Microsoft.SignalRService.ClientConnectionDisconnected: signalrservice-clientconnectiondisconnected

Example:

To send any event from event-grid to the function app:

You need to specify the repository name in the function URL, as request parameter repoName

Request Method: POST
Request URL: http://host/api/generic_triggers?repoName=TestGenericRepositoryDispatch

Example:

To trigger the workflow of the repository provided in function app URL(repoName), when the Machine Learning model is registered:

  On:
    repository_dispatch:
        types: [machinelearning-modelregistered]
  (...)

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

About

No description, website, or topics provided.

Resources

License

Code of conduct

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •  

Languages