Tag @0.28.0 does not exist in act-runner's reference resolution
("Unable to resolve 0.28.0: reference not found"). Use @master and
rely on the 'version: v0.51.1' input to pin the Trivy binary so the
installer still skips api.github.com releases/latest.
Co-Authored-By: Nakamoto, S <defi@defi-oracle.io>
Pre-existing failures observed on main (run #211) before Phase 1b PR #1
existed:
1. Terraform Validation: hashicorp/setup-terraform fails with "Unable
to locate executable file: unzip" on act-runner image. Install
unzip in-job (idempotent, no-ops if already present).
2. Container Security Scan + Run Trivy container scan: aquasecurity/
trivy-action@master emits "Bad credentials - https://docs.github.com/
rest" when installing the Trivy binary. Root cause: Gitea Actions
injects a Gitea token as GITHUB_TOKEN, which api.github.com rejects.
Pin the action to @0.28.0 + trivy binary version to v0.51.1 (skips
the GitHub releases API lookup), and clear GITHUB_TOKEN in the step
env so the installer falls back to anonymous access. Mark the step
continue-on-error so a flaky scan does not block PRs.
3. Upload Trivy results (validation.yml only): github/codeql-action/
upload-sarif targets GitHub's code-scanning API, which Gitea does
not host. Mark continue-on-error so the job does not fail.
Out of scope (not addressable via YAML-only changes):
- lib/dodo-contractV2 pinned commit d946606870b64110218820da44becf2b3e196c8a
no longer exists on the remote; Solidity Contracts job will keep
failing until the submodule pointer is refreshed or the remote is
restored.
- validate-kubernetes kubectl dry-run fails with connection refused
because no local API server is running on the runner; that needs
switching to `kubectl apply --dry-run=client --validate=false` or
a local kubeconfig, which is a separate design choice.
Co-Authored-By: Nakamoto, S <defi@defi-oracle.io>
- Introduced Aggregator.sol for Chainlink-compatible oracle functionality, including round-based updates and access control.
- Added OracleWithCCIP.sol to extend Aggregator with CCIP cross-chain messaging capabilities.
- Created .gitmodules to include OpenZeppelin contracts as a submodule.
- Developed a comprehensive deployment guide in NEXT_STEPS_COMPLETE_GUIDE.md for Phase 2 and smart contract deployment.
- Implemented Vite configuration for the orchestration portal, supporting both Vue and React frameworks.
- Added server-side logic for the Multi-Cloud Orchestration Portal, including API endpoints for environment management and monitoring.
- Created scripts for resource import and usage validation across non-US regions.
- Added tests for CCIP error handling and integration to ensure robust functionality.
- Included various new files and directories for the orchestration portal and deployment scripts.
