azure-deprecation / infrastructure Goto Github PK
View Code? Open in Web Editor NEWInfrastructure for running Azure Deprecation Notices
License: MIT License
Infrastructure for running Azure Deprecation Notices
License: MIT License
Provide API to unregister for CloudEvent notifications
Automatically tweet to @AzureEndOfLife for new notices
Provide automated deployment for Azure Functions for every main commit by using GitHub Actions
Automatically close expired notices GitHub issues given they are no longer applicable.
This should be done by subscribing to internal "deprecation expired" events after which we close the GitHub issue.
Depends on #36
Automatically tweet about deprecations that are expired.
This should be done by subscribing to internal "deprecation expired" events which uses the data to tweet.
Depends on #36
Provide capability to extend a deprecation so that:
Provide landing page in deprecation portal with information about:
Provide capability to specify deprecation timeline instead of just deprecation date.
For example: azure-deprecation/dashboard#79
Provide API to register for CloudEvent notifications.
It should automatically create the subscription and ensure it is validated.
Azure tags should be assigned with information about who requested it.
This allows us to look up the resource with Azure Resource Graph to manage it (get, list, update, delete).
It should be served through Azure API Management so that we can benefit from their analytics, user management and policies such as throttling and caching.
Use camel-casing for payload serialization on:
Provide API to update registration for CloudEvent notifications
Provide Google Form to suggest a new deprecation
Provide capability to automatically scan Azure subscriptions for impact so that portal shows the impact for the subscriptions linked to the logged in user.
Provide capability in portal to subscribe to updates for a given deprecation
Provide documentation on reminders such as a flow diagram
Provide documentation on general infrastructure that gives an idea of how things are running
Provide automatic persistance of new published deprecations so that we can query it to automate tweets, emails, issue closure, etc.
Provide automated reminders on open issues for upcoming deprecations.
This should be done automatically for every new issue with the following time periods:
These should be communicated via:
Depends on #36
Provide a generic process for dequeuing a message from Service Bus and pushing it as an event to Azure Event Grid topics.
We need this given we will schedule workloads which should be notified to all processes via events.
Provide summary newsletter for end-users to subscribe to which include the new deprecations of the past x weeks/month.
Provide alerts for exceptions, dead lettered messages, publish failed for events, Cosmos RUs, etc.
Provide a process that schedules notice expiry on a Service Bus queue.
It should:
Depends on #36
Provide capability in portal to subscribe for new deprecation notices
Migrate to .NET 6.x since 3.1 is going to be deprecated.
Provide capability to scan an Azure subscription and show impacted deprecations.
This should be based on Azure Resource Graph.
Provide automated deployment for Azure infrastructure for every main commit by using GitHub Actions.
Process new deprecation notices on our dashboard.
It should:
Provide control over notices by locking the conversation after posting a message to use Discussions to talk about deprecations.
Provide unique deprecation ID (id
) to existing published notices.
This allows us to re-use the ID in our event and use it as a partition key in Cosmos DB.
Provide documentation on deprecation expiry such as a flow diagram
Provide automated deploy of the core infrastructure to staging and production.
Provide page in portal to see all active deprecations
Provide API to get a user his registrations for CloudEvent notifications
Provide REST API endpoint to get all deprecations with filtering options by:
Provide Azure Resource Graph query on deprecation detail page that customers can run to assess impact.
API connections for new notice tweets are not correct
We should provide an API which allows us to post a new deprecation notice which translates it into our internal contract and gives it back to the consumer.
The API should provide OpenAPI specs with documentation and contract information about request/response.
Azure Automation Service Management REST APIs are being retired.
**Deadline:** April 30, 2019
**Impacted Services:** Azure Automation
**More information:** https://azure.microsoft.com/en-us/updates/azure-automation-service-management-rest-apis-are-being-retired-april-30-2019/
### Notice
> Azure Service Management (ASM) REST APIs for Azure Automation will be retired and no longer supported after April 30, 2019. Azure Resource Manager, our next-generation cloud infrastructure stack, fully replaces these APIs and provides many additional benefits, including:
> - Increased security with role-based access control (RBAC)
> - Support for resource grouping and tags
> - A streamlined deployment and management process
### Impact
> If you’re unsure whether you’re using Service Management REST APIs, check the URI referenced in your code or service. If it’s https://management.core.windows.net, you’re using Service Management REST APIs and you should migrate to Resource Manager REST APIs.
>
> If you’re unsure whether you’re using Service Management PowerShell cmdlets, check whether the cmdlet name includes AzureRM (for example, Get-AzureRmAutomationAccount) or Az (for example, Get-AzAutomationAccount). If it doesn’t include AzureRM or Az (for example, Get-AzureAutomationAccount), you should migrate to Resource Manager PowerShell cmdlets.
### Required Action
> Migrate any Azure Automation Service Management REST APIs and PowerShell cmdlets for Azure Automation to Resource Manager REST APIs or the latest PowerShell cmdlets by April 30, 2019, to take advantage of advanced capabilities and avoid any service disruptions.
Labels:
impact:action-required
, services:automation
Impacted Services
can be a comma separated listservices:{name}
, however, we should ignore this as this is just to allow people to filter issues by serviceimpact:action-required
, impact:limited
, impact:none
, impact:unknown
{
"notice": {
"title": "Azure Automation Service Management REST APIs are being retired",
"deprecationDate": "2019-04-30T00:00:00Z",
"announcementUrl": "https://azure.microsoft.com/en-us/updates/azure-automation-service-management-rest-apis-are-being-retired-april-30-2019/",
"impact": {
"action": "none|required|limited",
"services": [
"Azure Automation"
]
}
},
"github": {
"issueId": "2",
"state": "open",
"reportedBy": "TomKerkhove",
"createdAt": "2019-04-19T13:16:55Z",
"updatedAt": "2019-04-19T13:16:55Z",
"repoUrl": "https://github.com/azure-deprecation/dashboard"
}
}
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.