Arcus

Azure development in a breeze.

Issues & Feature Requests

We track issues in a variety of places for Arcus. If you have found an issue or have a feature request, please submit an issue to the below repositories.

Area	Description	Link
General	General request or suggestions for new areas	File an Issue
Event Grid	Requests & suggestions for Azure Event Grid integration	Features - File an Issue
Event Grid Sidecar	Requests & suggestions for Azure Event Grid Docker container	Features - File an Issue
Security	Requests & suggestions for security integration(s)	Features - File an Issue
Web API	Requests & suggestions for web api development	Features - File an Issue
Messaging	Requests & suggestions for messaging development	Features - File an Issue
Background Jobs	Requests & suggestions for reusable jobs & development of background jobs	Features - File an Issue
Observability	Requests & suggestions for adding observability to applications	Features - File an Issue
.NET Templates	Requests & suggestions for .NET templates to get started	Features - File an Issue
Machine Learning	Requests & suggestions for machine learning	Features - File an Issue
Azure Machine Learning	Requests & suggestions for machine learning in Azure	Features - File an Issue

Starting a new components

Every new Arcus component repo should be created via following flow:

• Create a new repo based on our GitHub template which is located in arcus-azure/arcus.template.
  • We typically use the arcus.{component-name} naming convention
• Run the GitHub Repo Configurator to generate all default labels, issues and milestoned.
  • Add arcus-automation with Admin permissions to your new repo
  • Run the tool as arcus-automation
• Get started!

We have a variety of Azure DevOps YAML templates which you can re-use and are open for suggestion!

Customers

Are you an Arcus user? Let us know and get listed!

Contributing

We are open for all contributions, learn more about our coding conventions in our "Developer Guide".