Skip to content

Demo: block an intentionally vulnerable container release - #74

Open
DevOpsAIguru123 wants to merge 28 commits into
mainfrom
agent/container-image-release-advisor
Open

Demo: block an intentionally vulnerable container release#74
DevOpsAIguru123 wants to merge 28 commits into
mainfrom
agent/container-image-release-advisor

Conversation

@DevOpsAIguru123

Copy link
Copy Markdown
Owner

What changed

  • adds a self-contained policy-driven container image release advisor
  • provides independent Google ADK/Vertex AI and Claude Agent SDK/Sonnet 5 workflows
  • combines SonarCloud code analysis, pre-build Trivy misconfiguration scanning, exact-image vulnerability and secret scanning, deterministic release policy, protected approval, and Docker Hub publishing
  • produces pre-build, image-security, and consolidated HTML/PDF reports
  • adds a numbered architecture diagram using documented vendor brand assets
  • adds five-minute setup, authentication/WIF, successful and blocked demos, and production-readiness guidance

Security boundary

The AI advisor is informational only. It cannot approve, reject, waive, publish, or change the deterministic release policy. policy_decision: not_evaluated is never treated as approval.

No credentials, account IDs, generated reports, caches, session databases, or machine-local paths are included. GitHub Actions are SHA-pinned, and Trivy secret scanning reports no findings.

Configuration note

The two release workflows use workflow_dispatch by default because this repository does not yet have the documented SonarCloud, model-provider, Docker Hub, and protected-environment settings. Enable pull_request or push triggers only after completing the included setup guide.

Validation

  • catalog validation: 79 entries
  • repository tests: 72 passed
  • ADK unit tests: 28 passed
  • Claude adapter tests: 11 passed
  • workflow YAML parsing passed
  • shell syntax and SVG validation passed
  • action SHA pinning check passed
  • staged credential/local-reference checks passed
  • Trivy filesystem secret scans passed for the agent and workflow files

Vinod V and others added 4 commits July 28, 2026 17:22
Bumps the non-breaking-updates group in /agents/adk/terraform-plan-reviewer/terraform/gcs-sample with 1 update: [hashicorp/google](https://github.com/hashicorp/terraform-provider-google).


Updates `hashicorp/google` from 7.41.0 to 7.42.0
- [Release notes](https://github.com/hashicorp/terraform-provider-google/releases)
- [Changelog](https://github.com/hashicorp/terraform-provider-google/blob/main/CHANGELOG.md)
- [Commits](hashicorp/terraform-provider-google@v7.41.0...v7.42.0)

---
updated-dependencies:
- dependency-name: hashicorp/google
  dependency-version: 7.42.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: non-breaking-updates
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: tuximac <tuximac@tuximacs-MBP.hsd1.tx.comcast.net>
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@DevOpsAIguru123 DevOpsAIguru123 changed the title Add container image release advisor Demo: block an intentionally vulnerable container release Jul 30, 2026
@DevOpsAIguru123

Copy link
Copy Markdown
Owner Author

This PR is preserved as the isolated findings demonstration. It intentionally exercises SonarQube and Trivy against an unsafe release candidate so the screenshots and Actions evidence show the deterministic BLOCKED outcome.

Reusable production code is now proposed separately in #78. That PR removes deployable vulnerable fixtures, fixes workflow selection to the hardened assets, and retains fail-closed coverage through synthetic policy tests. Do not merge this demonstration PR into a release branch.

@DevOpsAIguru123
DevOpsAIguru123 marked this pull request as ready for review July 30, 2026 20:14
* add container image release advisor

* test ADK pipeline on pull requests

* make Claude the default PR advisor

* simplify Claude advisory report

* clarify human release approval status

* order release summary and link artifacts

* demonstrate blocked vulnerable release

* continue blocked demo for full security evidence

* collect complete security evidence before gating

* accept bounded triage identifiers in Claude review

* place Claude review after deterministic summary

* clarify consolidated report for readers

* deliver security reports by email and Discord

* retry transient Claude advisory failures

* bound Claude provider retries with timeouts

* retry Claude subprocess failures three times

* isolate Claude retries in bounded processes

* fix Claude retry shell parsing

* fallback to bounded Anthropic API transport

* shorten Claude SDK circuit breaker

* render fallback report in project environment

* update container release architecture diagram

* harden container advisor distribution

* add Sonar coverage and path safeguards

* trace subprocess policy coverage

* scope coverage to deterministic security core
@sonarqubecloud

Copy link
Copy Markdown

Quality Gate Failed Quality Gate failed

Failed conditions
C Security Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants