You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enhance Azure Rambi services with new guidelines, storage queue integration, and improved Docker configurations
- Updated coding instructions with Azure best practices and architecture patterns.
- Added storage queue binding for movie posters events.
- Modified Bicep modules to include storage account and queue configurations.
- Adjusted Dockerfile to expose port 80 for FastAPI service.
- Implemented CloudEvent handling for Azure Storage Queue messages in the movie gallery service.
- Enhanced movie entity to include internal poster URL.
- Updated requirements to include necessary packages for new features.
-@azure Rule - Use Azure Best Practices: When generating code for Azure, running terminal commands for Azure, or performing operations related to Azure, invoke your `get_azure_best_practices` tool if available.
1
+
# Azure Rambi Coding Instructions
2
+
3
+
## Azure Guidelines
4
+
-@azure Rule - Use Azure Best Practices: When generating code for Azure, running terminal commands for Azure, or performing operations related to Azure, invoke your `get_azure_best_practices` tool if available.
5
+
- Use Infrastructure as Code (IaC) with Bicep for all Azure deployments
6
+
- Prefer Azure Container Apps for microservices deployment
7
+
- Use Managed Identity for authentication when possible
8
+
- Configure proper RBAC permissions with least privilege
9
+
10
+
## Architecture Patterns
11
+
- Follow microservices architecture principles
12
+
- Implement the DAPR sidecars pattern for service-to-service communication
13
+
- Use API Management for API exposure and governance
14
+
- Implement proper error handling and retry logic
15
+
16
+
## Service-Specific Guidelines
17
+
-**Movie Generator Service**: Use Azure OpenAI with gpt-4o model
18
+
-**Movie Poster Service**: Use Azure OpenAI with dall-e-3 model
19
+
-**Movie Gallery Service**": Use DAPR components.
20
+
-**GUI Service**: Follow Flask best practices with proper templating
21
+
22
+
## Security Requirements
23
+
- Never hardcode credentials; use Key Vault references
24
+
- Implement proper error handling that doesn't leak sensitive information
25
+
- Follow secure networking practices
26
+
- Enable encryption for data at rest and in transit
27
+
28
+
## Performance Guidelines
29
+
- Implement caching where appropriate (especially for movie data)
@description('This is the built-in Key Vault Secrets Officer role. See https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles/security#key-vault-secrets-user')
0 commit comments