Closed
Conversation
…on, and billing discovery Rewrite the migration-to-aws plugin from a 4-phase to a 6-phase workflow (discover → clarify → design → estimate → generate → feedback) with three parallel discovery paths: infrastructure, application code, and billing. Key changes: Discover phase: - Add app-code discovery path scanning source for AI/ML frameworks (Gemini, Vertex AI, OpenAI, traditional ML like TensorFlow/PyTorch) - Add billing discovery path with GCP billing export analysis - Enhance IaC discovery with improved Terraform resource clustering using typed-edge strategy and classification rules Clarify phase: - Implement adaptive category-based questioning (global, compute, database, AI, AI-only) that activates based on discover findings - Skip categories when discover already provides sufficient signal Design phase (new): - Separate design from discover with dedicated design-infra, design-ai, and design-billing reference documents - Source-specific AI model mapping via ai-gemini-to-bedrock and ai-openai-to-bedrock reference tables Estimate phase: - Split into estimate-infra, estimate-ai, and estimate-billing - Add pricing-cache with validated rates and confidence levels - Use awspricing MCP server for real-time price validation Generate phase: - Produce Terraform configurations from templates (main.tf, variables.tf) - Generate AI provider adapter (provider_adapter.py) for SDK migration - Generate Bedrock setup scripts and comparison test harnesses - Add billing artifact generation and documentation artifacts - Structured artifact specs for infra, AI, billing, docs, and scripts Feedback phase (new): - Anonymized telemetry trace capturing phase timings, confidence scores, and migration complexity metrics - No PII or source code in traces Supporting changes: - Add JSON schemas for discover-ai, discover-billing, discover-iac, estimate-infra, and phase-status data structures - Update plugin.json version and README - Enhance design-refs with confidence levels, factual corrections, and improved service mapping tables Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Scott Schreckengaust <345885+scottschreckengaust@users.noreply.github.com>
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
There was a problem hiding this comment.
Semgrep OSS found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.
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
3 participants
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.
Exclude SemGrepOSS findings for generic OpenAI
Related
Changes
add exclusion rule
ai.generic.detect-generic-ai-oai.detect-generic-ai-oaifor semgrepAcknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.