Skip to content

feat(catalog): BE-9509 declare airgapSupport on every component version - #834

Merged
emre-guler merged 1 commit into
developfrom
feature/be-9509
Oct 14, 2026
Merged

emre-guler merged 1 commit into
developfrom
feature/be-9509

Conversation

@emre-guler

Copy link
Copy Markdown
Member

Summary

BE-9509: every component.yaml now declares whether the step can run in an air-gapped self-hosted installation.

platform: Common
airgapSupport: true
  • true: the step runs offline, uses only internal services, goes through the customer's artifact proxy, or takes an input that points it to an internal service.
  • false: the step needs public SaaS or internet, or it needs a code change before it can run air-gapped.

The values come from the component network inventory (Linear project doc "08. Component Network Inventory"). Every version of a component takes its component's verdict. One line is inserted as line 2 of each file; nothing else in the file changes, and the BOM and trailing newlines are preserved.

A new GitHub Actions check, Validate airgapSupport, fails when a component.yaml:

  • has no valid airgapSupport: true|false line;
  • has more than one such line;
  • is not at <component>/<version>/component.yaml.

It only blocks a merge once it is set as a required status check. The README documents the field.

Core counterpart: appcircleio/ac-lib-core (BE-9509).

🤖 Generated with Claude Code

Every component.yaml declares whether the step can run in an air-gapped
self-hosted installation. Values come from the component network
inventory. A GitHub Actions check fails when a component.yaml has no
valid airgapSupport line.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@emre-guler
emre-guler merged commit 5ce44ac into develop Oct 14, 2026
1 check passed
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.

1 participant