Feat/azure native migration#4
Merged
Aparnap2 merged 22 commits intoagent/invoicify-ai-servicefrom Mar 7, 2026
Merged
Conversation
NEW FILES: - DEPLOY.md - Quick start deployment (5 minutes) - DEPLOYMENT_GUIDE.md - Complete step-by-step guide - scripts/deploy-to-azure.sh - Automated deployment script FEATURES: ✅ Automated script creates all Azure resources ✅ Azure Container Apps deployment (recommended) ✅ Azure Functions option (serverless) ✅ Azure App Service option (traditional) ✅ Key Vault integration for secrets ✅ Container Registry setup ✅ CI/CD pipeline with GitHub Actions ✅ Cost optimization ($0-10/month) ✅ Security best practices ✅ Troubleshooting guide ✅ Post-deployment verification COST: - Free tier eligible - Estimated: $0-10/month Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
SECURITY FIRST: ✅ No hardcoded credentials (tenant ID, subscription ID removed) ✅ All secrets via GitHub Secrets + Key Vault ✅ .env.azure.example template for users ✅ Pre-commit secret scanning active NEW FILES: - infra/main.bicep - Complete Azure infrastructure (810 lines) - .github/workflows/deploy.yml - CI/CD pipeline - scripts/bootstrap.sh - One-command Azure setup - scripts/seed-keyvault.sh - Key Vault secret seeding - .env.azure.example - Azure credentials template UPDATED: - DEPLOY.md - Complete deployment guide - .gitignore - Added .env.azure.example to allowed files AZURE SERVICES (All Free Tier): ✅ Container Apps (API + Worker + Beat) - Free always ✅ PostgreSQL Flexible B1MS - Free 12 months ✅ Service Bus Standard - Free 12 months (replaces Redis) ✅ Blob Storage 5GB - Free 12 months ✅ Container Registry - Free 12 months ✅ Document Intelligence 500 pages - Free 12 months ✅ AI Search - Free always ✅ Key Vault - Free 12 months ✅ Event Grid - Free always ✅ Static Web Apps - Free always COST: $0/month for 12 months, ~$42/month after USAGE: 1. cp .env.azure.example .env.azure 2. Edit .env.azure with your Azure credentials 3. Run: ./scripts/bootstrap.sh 4. Add GitHub Secrets (displayed by script) 5. Push to main - auto-deploys Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
…alents - Add invoicify-worker/Dockerfile (Node 20 Alpine - replaces wrangler) - Add apps/azure-api/Dockerfile + main.py (Hono→FastAPI port for Azure Container Apps) - Add apps/azure-api/requirements.txt - Update apps/agent-core/src/config.py (Azure env defaults, remove Ollama/Neo4j) - Update apps/agent-core/src/extraction/azure_extractor.py (Azure DI + OpenRouter) - Update apps/agent-core/pyproject.toml (remove qdrant/upstash/sarvam/docling, add azure-ai) - Update apps/agent-core/Dockerfile (remove poppler/tesseract - not needed with Azure DI) - Add apps/agent-core/src/queue/azure_queue.py (Storage Queue consumer) - Add .github/workflows/azure-deploy.yml (correct monorepo CI/CD) - Add infra/main.bicep corrections via AZURE_DEPLOY_CHECKLIST.md
CHANGES: - apps/agent-core/src/main.py: Add queue consumer lifecycle hooks - invoicify-worker/package.json: Add Azure SDK + Node server deps QUEUE CONSUMER: ✅ Starts on FastAPI startup (background task) ✅ Graceful shutdown on app stop ✅ Silently skips if AZURE_STORAGE_CONNECTION_STRING not set ✅ Calls run_pipeline() for each invoice WORKER DEPS: ✅ @azure/storage-blob - Blob storage access ✅ @azure/storage-queue - Queue consumer ✅ @hono/node-server - Node.js server for Azure ✅ pg - Postgres client ✅ tsx - TypeScript execution for dev ✅ @types/pg - TypeScript types LOCAL DEV: cd invoicify-worker && pnpm install && pnpm dev:node NEXT: Test locally, then push to trigger CI/CD Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
CHANGES: - README.md - Complete rewrite with: - Updated architecture (Azure-native) - Monorepo structure documentation - Azure services table (free tier) - Quick start guide - Testing instructions - Security section - Cost breakdown - DEPLOY.md - Updated with: - Correct architecture (no Celery) - Node.js worker instead of Python - Azure Storage Queue instead of Service Bus - Updated component descriptions ACCURACY: ✅ Reflects actual codebase structure ✅ Documents Azure services correctly ✅ Shows free tier limits ✅ Includes local dev instructions ✅ CI/CD pipeline documented Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
CHANGES: - prd.md - Complete rewrite with: - Azure-native architecture - Free tier cost breakdown - Updated user stories - Technical specifications - Timeline (MVP complete ✅) - Open questions - ARCHITECTURE.md - New comprehensive guide: - Monorepo structure - Component design (FastAPI + Node.js) - Database schema (PostgreSQL) - API design (OpenAPI) - Infrastructure (Bicep) - Security (Key Vault + RBAC) - Scalability (auto-scaling + caching) - Monitoring (Azure Monitor) ACCURACY: ✅ Reflects actual codebase ✅ Documents Azure services correctly ✅ Shows free tier limits ✅ Includes database schema ✅ API endpoints documented Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
REMOVED: - AZURE_MIGRATION_SUMMARY.md (superseded by DEPLOY.md) - CLOUDFLARE_MIGRATION_PLAN.md (no longer using Cloudflare) - IMPLEMENTATION_COMPLETE*.md (superseded by README.md) - MIGRATION_SUMMARY.md (migration complete) - README_STATUS.md (README is now complete) - TEST_RESULTS.md (tests documented in README) - TRANSFORMATION_PROGRESS.md (transformation complete) KEPT: - README.md (main documentation) - DEPLOY.md (deployment guide) - DEPLOYMENT_GUIDE.md (detailed deployment) - prd.md (product requirements) - ARCHITECTURE.md (system architecture) - DOCKER_TESTING_GUIDE.md (local testing) - CONTRACT_VERIFICATION.md (reference) Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
- Add Pydantic schemas for workflow state and step results - Add PostgreSQL schema with asyncpg helpers - Implement deterministic fraud gate (bank detail changes, vendor mismatches) - Implement duplicate detection (exact + fuzzy matching) - Implement 3-way matching with Azure AI Search vectors - Implement GL coding with memory-based historical lookup - Implement HITL task creation (draft resolution packets) - Implement append-only audit logger - Create LangGraph workflow with all nodes - Add unit and integration tests BREAKING CHANGE: New database schema required
NEW FILE: - IMPLEMENTATION_SUMMARY.md - Complete project overview CONTENTS: ✅ Executive summary with key metrics ✅ Architecture overview (ASCII diagram) ✅ Monorepo structure ✅ All 7 implementation phases (complete) ✅ Test results (51 unit + 7 E2E) ✅ Cost breakdown (bash for 12 months) ✅ Security measures ✅ Deployment instructions ✅ Key features ✅ Metrics & KPIs ✅ Technology stack ✅ Timeline ✅ Documentation index ✅ Completion checklist ✅ Next steps PURPOSE: - Single source of truth for project status - Onboarding document for new team members - Reference for stakeholders - Interview pitch preparation Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
PHASE 1 - DELETE VOICE-AGENT (575MB saved): ✅ Removed apps/voice-agent/ (unused Sarvam STT prototype) ✅ 12 files deleted, 440MB code + 575MB .venv gone PHASE 2 - DIRECT POSTGRES STATUS UPDATES: ✅ Created src/db/status.py - Direct Postgres writer ✅ Updated src/main.py - Swapped import (drop-in replacement) ✅ Created migrations/001_add_invoice_status_tracking.sql ✅ Updated src/config.py - Removed edge_api_base_url field ✅ Updated module docstring (Azure-native, no Cloudflare) WHY THIS MATTERS: - Old code called http://host.docker.internal:8787 (Cloudflare Worker) - That URL is unreachable in Azure Container Apps - Status updates were silently failing in production - Now writes directly to Postgres invoices table MIGRATION REQUIRED: Run once: psql $DATABASE_URL -f migrations/001_add_invoice_status_tracking.sql NEXT (PHASE 3-4): - Test status updates work - Delete src/utils/edge_callback.py - Delete apps/edge-api/ (Cloudflare Worker) Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
…back DELETED: - apps/edge-api/ (Cloudflare Worker, replaced by Postgres direct writes) - apps/api/ (Azure Functions prototype, unused) - src/utils/edge_callback.py (replaced by src/db/status.py) REMAINING ACTIVE APPS: - apps/agent-core/ (Python FastAPI) - invoicify-worker/ (TypeScript Hono API) - apps/web/ (Next.js frontend) Total cleanup: ~100MB legacy code removed Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
…ation BREAKING CHANGES: - Replaced Salesforce with HubSpot CRM throughout codebase - MCP SDK updated to use FastMCP (not lowlevel Server) FILES CHANGED: - quickbooks_mcp.py: Fixed import (Server → FastMCP), added .env loading - hubspot_mcp.py: NEW - HubSpot CRM integration with 6 tools - registry.py: Replaced Salesforce with HubSpot - config.py: Removed SF fields, added HS field - .env.azure.example: Updated with HubSpot setup instructions - Documentation: 3 files updated (Salesforce → HubSpot) - Tests: 22 new HubSpot MCP tests SMOKE TEST RESULTS: ✅ QuickBooks: Server initialized (401 = tokens expired, needs refresh) ✅ HubSpot: Server initialized, company created ✓, deal creation needs fix NEXT STEPS: 1. Refresh QuickBooks tokens (curl command in DEPLOY.md) 2. Fix HubSpot deal creation payload (associations format) 3. Run full test suite Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
…aid diagrams README.md: - 3 new Mermaid diagrams (sequence, class, state) - Updated test count: 51 → 83 - Added MCP integration badge - Better formatting and mobile-friendly tables PRD.md: - Version 5.0 (HubSpot Integration) - Replaced Salesforce with HubSpot throughout - Added HubSpot Private App token flow - Updated demo story (HubSpot Deal → Invoice Paid) ARCHITECTURE.md: - Version 4.1 (HubSpot Integration) - Removed deleted apps (api, edge-api, voice-agent) - Added HubSpot MCP Server section (6 tools) - Updated security section (Private App token) IMPLEMENTATION_SUMMARY.md: - Version 4.1 (HubSpot Integration) - Tests: 51 → 83 passing - Coverage: 57% → 82% - Added Phase 3.5: HubSpot ✅ Complete - Documentation: 3,267 → 4,100+ lines All docs now accurate and consistent with current state. Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (230)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request marks a significant architectural shift, transitioning the entire application to an Azure-native cloud environment. The core purpose is to enhance scalability, reliability, and cost-efficiency by fully embracing Azure's ecosystem. This migration also introduces a robust integration with HubSpot CRM, expanding the application's capabilities in managing customer relationships alongside financial processes. The changes streamline the deployment process and ensure the system is production-ready with comprehensive testing and documentation. Highlights
Changelog
Ignored Files
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request represents a major migration of the application's backend from a Cloudflare-based stack to an Azure-native architecture. It introduces a significant number of new components, including Azure service integrations for storage, queues, and AI, as well as new documentation and MCP servers for QuickBooks and HubSpot. My review focuses on the new architecture's robustness, correctness, and maintainability. I've identified a critical issue with the QuickBooks OAuth token management that will cause failures in a containerized environment, a high-severity issue with the database connection logic, and a flawed idempotency check. I've also included several medium-severity comments on documentation and script correctness to improve clarity and prevent potential issues.
Note: Security Review did not run due to the size of the PR.
Comment on lines
+300
to
+381
| def _load_tokens_from_file(self) -> None: | ||
| """ | ||
| Load cached tokens from .secrets/qb_tokens.json. | ||
|
|
||
| Only loads if access_token is not expired. | ||
| """ | ||
| if not TOKEN_FILE_PATH.exists(): | ||
| logger.debug( | ||
| "token_file_not_found", | ||
| trace_id=self._trace_id, | ||
| path=str(TOKEN_FILE_PATH), | ||
| ) | ||
| return | ||
|
|
||
| try: | ||
| data = json.loads(TOKEN_FILE_PATH.read_text()) | ||
| expires_at = data.get("expires_at", 0) | ||
|
|
||
| # Check if tokens are still valid (with 5-minute buffer) | ||
| if time.time() < expires_at - 300: | ||
| self._access_token = data.get("access_token") | ||
| self._refresh_token = data.get("refresh_token") | ||
| self._expires_at = expires_at | ||
| self.realm_id = data.get("realm_id", self.realm_id) | ||
|
|
||
| logger.info( | ||
| "tokens_loaded_from_file", | ||
| trace_id=self._trace_id, | ||
| expires_in_seconds=int(expires_at - time.time()), | ||
| ) | ||
| else: | ||
| logger.info( | ||
| "tokens_expired_in_file", | ||
| trace_id=self._trace_id, | ||
| expired_ago_seconds=int(time.time() - expires_at), | ||
| ) | ||
| except Exception as e: | ||
| logger.warning( | ||
| "token_file_load_failed", | ||
| trace_id=self._trace_id, | ||
| error=str(e), | ||
| ) | ||
|
|
||
| def _save_tokens_to_file(self) -> None: | ||
| """ | ||
| Save tokens to .secrets/qb_tokens.json. | ||
|
|
||
| Persists both access_token and refresh_token for future use. | ||
| """ | ||
| if not self._access_token or not self._refresh_token: | ||
| logger.warning( | ||
| "token_save_skipped_missing_tokens", | ||
| trace_id=self._trace_id, | ||
| ) | ||
| return | ||
|
|
||
| try: | ||
| TOKEN_FILE_PATH.parent.mkdir(parents=True, exist_ok=True) | ||
| data = { | ||
| "access_token": self._access_token, | ||
| "refresh_token": self._refresh_token, | ||
| "expires_at": self._expires_at, | ||
| "realm_id": self.realm_id, | ||
| } | ||
| TOKEN_FILE_PATH.write_text(json.dumps(data, indent=2)) | ||
|
|
||
| # Set restrictive permissions (owner read/write only) | ||
| os.chmod(TOKEN_FILE_PATH, 0o600) | ||
|
|
||
| logger.info( | ||
| "tokens_saved_to_file", | ||
| trace_id=self._trace_id, | ||
| path=str(TOKEN_FILE_PATH), | ||
| expires_in_seconds=int(self._expires_at - time.time()) if self._expires_at else None, | ||
| ) | ||
| except Exception as e: | ||
| logger.error( | ||
| "token_save_failed", | ||
| trace_id=self._trace_id, | ||
| error=str(e), | ||
| ) | ||
|
|
There was a problem hiding this comment.
The TokenManager for QuickBooks stores the OAuth 2.0 access and refresh tokens in a local file (.secrets/qb_tokens.json). This approach is not suitable for a stateless, containerized environment like Azure Container Apps for several critical reasons:
- Statelessness: If the container restarts, the local file system is wiped, and the tokens are lost.
- Scalability: If the service is scaled to multiple instances, each instance will have its own local token file, leading to token conflicts and authentication failures.
- Token Rotation: QuickBooks refresh tokens are single-use. After a single restart and re-authentication, the original refresh token from the environment will be invalid, causing all subsequent authentication attempts to fail permanently until the environment variable is manually updated.
A shared, persistent storage mechanism like Azure Cache for Redis or a database table should be used to store and manage these tokens across all instances and restarts.
Comment on lines
+41
to
+57
| _pool = await asyncpg.create_pool( | ||
| host=settings.database_url.split("@")[1].split(":")[0] | ||
| if "@" in settings.database_url | ||
| else "localhost", | ||
| port=5432, | ||
| user=settings.database_url.split(":")[1].replace("//", "") | ||
| if "//" in settings.database_url | ||
| else "invoicify", | ||
| password=settings.database_url.split(":")[2].split("@")[0] | ||
| if "@" in settings.database_url | ||
| else "password", | ||
| database=settings.database_url.split("/")[-1] | ||
| if "/" in settings.database_url | ||
| else "invoicify", | ||
| min_size=2, | ||
| max_size=10, | ||
| ) |
There was a problem hiding this comment.
The manual parsing of the database_url string is fragile and can easily break if the URL format changes slightly (e.g., no password, different options). This also includes hardcoded default credentials if parsing fails, which is not a safe practice. Pydantic and pydantic-settings provide robust parsing for database connection strings via the PostgresDsn type. Using this would make the connection logic more robust and less error-prone.
I recommend updating config.py to use PostgresDsn for database_url and then simplifying this function to use the DSN directly.
_pool = await asyncpg.create_pool(
dsn=str(settings.database_url),
min_size=2,
max_size=10,
)
Comment on lines
+118
to
+143
| # Check idempotency | ||
| exists, existing_id, existing_status = await db.check_idempotency(state.idempotency_key) | ||
|
|
||
| if exists: | ||
| logger.warning( | ||
| "node_ingest_duplicate", | ||
| trace_id=trace_id, | ||
| existing_id=str(existing_id), | ||
| status=existing_status, | ||
| ) | ||
|
|
||
| result = IngestResult( | ||
| node_name=NodeName.INGEST, | ||
| confidence=1.0, | ||
| reasons=["Invoice already processed"], | ||
| status="skipped", | ||
| idempotency_key=state.idempotency_key, | ||
| is_duplicate=True, | ||
| existing_invoice_id=existing_id, | ||
| ) | ||
|
|
||
| return { | ||
| "ingest_result": result.model_dump(), | ||
| "invoice_status": existing_status, | ||
| "error_message": "Duplicate invoice - skipped processing", | ||
| } |
There was a problem hiding this comment.
The idempotency check in the ingest_node is based on a preliminary key derived from trace_id. This only prevents processing the same job twice, but it does not prevent processing a duplicate invoice if it arrives in a different job with a new trace_id. A true idempotency check should be based on a hash of the invoice's unique content (e.g., vendor, invoice number, date, amount), which is only available after the extraction step. This check should be moved to a later stage in the workflow, after extract_node, to ensure true idempotency and prevent duplicate payments.
| # ── Extractor mode ──────────────────────────────────────────────────────────── | ||
| # Options: fixture | azure_di | ollama | sarvam | ||
| # Use 'fixture' for local dev without Azure keys | ||
| EXTRACTOR_MODE=fixture |
There was a problem hiding this comment.
The environment variable EXTRACTOR_MODE is defined here and again on line 91. This redundancy can be confusing as the last one will take precedence. To improve clarity and avoid potential configuration errors, please remove one of the definitions to have a single source of truth for this setting.
Comment on lines
+428
to
+438
| CREATE TABLE invoices ( | ||
| ... | ||
| idempotency_key VARCHAR(64) UNIQUE, | ||
| trace_id VARCHAR(36) DEFAULT gen_random_uuid(), | ||
| current_node VARCHAR(50), | ||
| fraud_check_passed BOOLEAN, | ||
| duplicate_check_passed BOOLEAN, | ||
| three_way_match_confidence DECIMAL(5,4), | ||
| gl_code VARCHAR(20), | ||
| human_task_id UUID REFERENCES human_tasks(id) | ||
| ); |
There was a problem hiding this comment.
The CREATE TABLE invoices statement here re-defines the table already created on line 404. It appears the intent was to show the addition of new columns for the AP workflow. Using CREATE TABLE again is incorrect and will cause an error if the script is run. This should be an ALTER TABLE statement to add the new columns. For example:
-- Add new columns to invoices table for AP workflow
ALTER TABLE invoices
ADD COLUMN idempotency_key VARCHAR(64) UNIQUE,
ADD COLUMN trace_id VARCHAR(36) DEFAULT gen_random_uuid(),
ADD COLUMN current_node VARCHAR(50),
ADD COLUMN fraud_check_passed BOOLEAN,
ADD COLUMN duplicate_check_passed BOOLEAN,
ADD COLUMN three_way_match_confidence DECIMAL(5,4),
ADD COLUMN gl_code VARCHAR(20),
ADD COLUMN human_task_id UUID REFERENCES human_tasks(id);
README.md
Outdated
|
|
||
| [](https://github.com/Aparnap2/invoicify) | ||
| [](https://github.com/Aparnap2/invoicify) | ||
| [](https://github.com/Aparnap2/invoicify/tree/feat/azure-native-migration) |
There was a problem hiding this comment.
There are a couple of inconsistencies in the project's documentation that could cause confusion:
- The branch name in the badge on this line is
feat/azure--native--migration(with a double dash), which appears to be a typo. - The version mentioned in this file (
Version: 4.0) conflicts with the version inARCHITECTURE.md(Version: 4.1).
Please align these details across the documentation for consistency.
Comment on lines
+48
to
+57
| \d invoices | ||
|
|
||
| -- Show row count | ||
| SELECT COUNT(*) as invoice_count FROM invoices; | ||
|
|
||
| -- Show sample of existing data | ||
| SELECT id, trace_id, status, created_at, updated_at | ||
| FROM invoices | ||
| ORDER BY created_at DESC | ||
| LIMIT 5; |
There was a problem hiding this comment.
The SQL statements \d invoices and the final SELECT query are for manual verification and are not part of a standard migration script. These commands are specific to psql and will cause errors when run by most automated database migration tools. Please remove them from the script to ensure it can be executed cleanly by automation.
HIGH PRIORITY: ✅ TokenManager: Use Redis for stateless token storage (Azure Container Apps compatible) ✅ Database connection: Use PostgresDsn (no manual parsing, no hardcoded creds) ✅ Idempotency: Content-based hash check (not just trace_id) MEDIUM PRIORITY: ✅ Duplicate detection: SHA256 hash of vendor+invoice_number+date+amount ✅ Token store: Redis-backed with graceful degradation LOW PRIORITY: ✅ .env.azure.example: Remove duplicate EXTRACTOR_MODE ✅ Migration script: Use ALTER TABLE (not CREATE TABLE twice) ✅ Migration script: Remove psql-specific commands ✅ README badge: Fix branch name (single dash) ✅ Version: Update to v4.1 (consistent with ARCHITECTURE.md) FILES CHANGED: - src/db/token_store.py (NEW - Redis token store) - src/utils/hashing.py (NEW - invoice content hash) - src/mcp_servers/quickbooks_mcp.py (Redis integration) - src/db/db.py (PostgresDsn + duplicate check) - src/config.py (PostgresDsn type) - src/graph/ap_workflow.py (content hash check) - .env.azure.example (remove duplicate) - 001_add_invoice_status_tracking.sql (fix ALTER TABLE) - README.md (fix badge + version) - schema.sql (add content_hash column) Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.