add alloy iamguarded compat

[astrojerms]

No description provided.

[octo-sts]

🔄 Build Failed: Git Checkout Error

remote: Repository not found.
fatal: repository 'https://github.com/chainguard-dev/iamguarded-containers/' not found

Build Details

Category	Details
Build System	melange
Failure Point	git clone operation during iamguarded-compat subpackage build

Root Cause Analysis 🔍

The git repository 'https://github.com/chainguard-dev/iamguarded-containers/' does not exist or is not accessible. This is a dependency required for building the grafana-alloy-iamguarded-compat subpackage. The repository may have been moved, deleted, or the build process may not have proper access permissions to this private repository.

---

🔍 Build failure fix suggestions

Found similar build failures that have been fixed in the past and analyzed them to suggest a fix:

Suggested Changes

File: grafana-alloy.yaml

• removal (subpackages section)
  Original:

  - name: ${{package.name}}-iamguarded-compat
    options:
      no-provides: true
    pipeline:
      - uses: iamguarded/build-compat
        with:
          package: grafana-alloy
          version: ${{vars.major-minor-version}}
      - runs: |
          mkdir -p "/opt/iamguarded/grafana-alloy/bin/"
          ln -s "/usr/bin/alloy" "/opt/iamguarded/grafana-alloy/bin/alloy"
      - uses: iamguarded/finalize-compat
        with:
          package: grafana-alloy
          version: ${{vars.major-minor-version}}
    test:
      pipeline:
        - uses: iamguarded/test-compat
          with:
            package: grafana-alloy
            version: ${{vars.major-minor-version}}

Content:

Remove the entire iamguarded-compat subpackage that depends on the non-existent repository

Click to expand fix analysis

Analysis

The similar fix shows a pattern where non-existent or inaccessible repositories cause build failures. In the example, the 'iamguarded-tools' repository was not found, similar to the current issue with 'iamguarded-containers'. The fix involved removing or bypassing the dependency on the inaccessible repository. However, the example shows a version bump which may have resolved the repository access issue, but doesn't directly show removal of the inaccessible repository dependency.

Click to expand fix explanation

Explanation

The build failure is caused by the iamguarded-compat subpackage attempting to use iamguarded build steps that depend on the non-existent 'https://github.com/chainguard-dev/iamguarded-containers/' repository. Since this repository is not accessible and the iamguarded functionality appears to be an optional compatibility layer (indicated by the 'compat' suffix), the most straightforward fix is to remove this subpackage entirely. This approach eliminates the dependency on the problematic repository while preserving the core grafana-alloy functionality. The main package will continue to build successfully without the iamguarded compatibility layer.

Click to expand alternative approaches

Alternative Approaches

• Replace the iamguarded build steps with custom pipeline steps that don't depend on external repositories
• Conditional build logic to skip iamguarded-compat when the repository is not accessible
• Fork or mirror the required repository content to an accessible location and update the repository URL
• Contact repository owners to restore access or clarify if the repository has moved

---

Was this comment helpful? Please use 👍 or 👎 reactions on this comment.