Conversation
…rrative improve project info scrape extraction and show placeholders when missing make assumptions module-aware + update assumptions prompt add historical estimates toggle to scale hours/rates + update subtask method labels persist report metadata and expose report list with links/downloads in UI update default scrape URL to new Google Doc
- Created BackendStack to manage App Runner service with ECR and Cognito integration. - Created FrontendStack to manage S3 bucket and CloudFront distribution for static assets. - Added package.json and package-lock.json for dependency management. - Configured TypeScript settings in tsconfig.json for the project.
…le state before deployment
…VPC configuration
- Deleted cdk.out files: cdk.out, manifest.json, and tree.json. - Updated the Postgres engine version in the backend stack from V15_5 to VER_15_15.
…remove waiting mechanism
… update README instructions
…validation step in deploy workflow
…tion ID, and report frontend URL
- Updated .env.example to include S3_REPORT_BUCKET and REPORTS_TABLE_NAME. - Enhanced main.py to integrate ReportRegistryService for report management. - Added new API endpoints for report payload retrieval and deletion. - Implemented report loading and overwriting functionality in the frontend (App.tsx, Reports.tsx). - Created Reports component for managing saved reports with options to load, overwrite, and delete. - Updated AWS deployment documentation to reflect new report storage architecture. - Added backend stack configuration for S3 bucket and DynamoDB table for report metadata.
…te routing for API Next
…teway integration
…dling - Introduced new ReportJob model for managing report generation jobs. - Added endpoints for queuing and retrieving report jobs. - Implemented self-invocation of Lambda functions for async job processing. - Enhanced AI service with configurable request timeout to prevent API 504 errors. - Updated frontend to support report job queuing and status checking. - Improved error handling and logging for report generation and subtask previews. - Updated environment variables in .env.example and README for new configurations.
…ion and add new infrastructure files for backend and frontend stacks
…nner resources - Updated `lambda_handler.py` to remove path normalization for legacy routes. - Added `get_current_identity` endpoint in `main.py` for lightweight auth validation. - Revised AWS deployment documentation to reflect changes in backend architecture. - Removed legacy App Runner and ECR references from README and deployment scripts. - Updated frontend to remove backend target selection and adjust API calls accordingly. - Cleaned up API configuration to eliminate legacy references. - Adjusted Vite configuration to remove proxy for `/api-next`. - Modified CDK stack definitions to focus on Lambda API deployment. - Deleted unused backend-next Lambda function code. - Updated local development script to remove legacy backend target option.
…uthentication flow
…h appropriate error handling
…port/subtask jobs
- Updated the infrastructure to provision new DynamoDB tables: Proposals, Proposal Versions, Proposal Documents, Contracts, and Contract Sync. - Enhanced the BackendLambdaStack to create and manage these tables, including global secondary indexes where necessary. - Implemented ContractStoreService and ProposalStoreService for managing contract and proposal data, respectively, with support for both DynamoDB and in-memory storage. - Added a script to sync DynamoDB table names to GitHub environment variables for deployment workflows. - Created unit tests for the new services to ensure functionality in memory mode.
…N dependency cycles
…ation status messages
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.
Update main branch