microservices-reference-implementation icon indicating copy to clipboard operation
microservices-reference-implementation copied to clipboard

A reference implementation demonstrating microservices architecture and best practices for Microsoft Azure

Results 8 microservices-reference-implementation issues
Sort by recently updated
recently updated
newest added

Followed the deployment guide at: https://github.com/mspnp/microservices-reference-implementation/blob/main/deployment.md till this line: az keyvault secret set --name Ingestion-Ingress-Tls-Key --vault-name $INGESTION_KEYVAULT_NAME --value "$(cat ingestion-ingress-tls.key)" with this error: cat: ingestion-ingress-tls.key: No such file or directory...

Feature Request. This application would be easier referenced if the container images were hosted in the GitHub container registry for mspnp, and the image details were used in the helm...

There is a 3 line script snippet which doesn't make sense to me. Why is the AI_KEY variable being set when it's never subsequently referenced anywhere else in the deployment.md...

The secrets-store.csi.x-k8s.io/v1alpha1 API is deprecated. The sample should shift to use secrets-store.csi.x-k8s.io/v1 instead. I'd supply a PR for this, however I'm also not clear why the script is using `cat

https://docs.microsoft.com/en-us/azure/architecture/microservices/model/microservice-boundaries#example-defining-microservices-for-the-drone-delivery-application Four aggregates — Delivery, Package, Drone, and Account — and two domain services, Scheduler and Supervisor. Delivery and Package are obvious candidates for microservices. The Scheduler and Supervisor coordinate...

upgrade the to the latest AppInsights-nodejs version since it is addressing some connections problems when using live metrics: https://github.com/microsoft/ApplicationInsights-node.js/issues/510

enhancement

The solution worked overall and I encountered the below issues. - Update export SP_DETAILS=$(az ad sp create-for-rbac --role="Contributor" -o json) ==> export SP_DETAILS=$(az ad sp create-for-rbac --role="Contributor" --roles="RGResourceID" -o json)...

Step below returns error where 1.24.7 is not available helm install nginx-ingress-dev stable/nginx-ingress --namespace ingress-controllers --version 1.24.7 --set rbac.create=true --set controller.ingressClass=nginx-dev