Skip to content

Slice 6: pass splunkbase_app_id to reusable release workflow #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pbujna-apius merged 1 commit into from
Jul 20, 2026
Merged

Slice 6: pass splunkbase_app_id to reusable release workflow #8

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 12 additions & 3 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,15 @@
name: release

# Caller for the shared release/publish workflow (ADR-0004 / ADR-0005).
# Caller for the shared release/publish workflow (ADR-0004 / ADR-0005 / ADR-0006).
# Triggered by pushing a vX.Y.Z tag (on the merged "Release vX.Y.Z" commit).
# Packages the app at the tag version, runs AppInspect (base blocking, cloud
# advisory by default), and publishes a GitHub Release. Splunkbase upload is
# out of scope (slice #6).
# advisory by default), publishes a GitHub Release, and then publishes to
# Splunkbase behind the `splunkbase` Environment approval gate (slice #6).
#
# splunkbase_app_id comes from the SPLUNKBASE_APP_ID repo variable; when it is
# unset the shared workflow skips the Splunkbase publish (first publish is
# manual). SPLUNK_USER/SPLUNK_PASS reach the reusable workflow via
# `secrets: inherit` and are scoped to the `splunkbase` Environment for publish.
on:
push:
tags:
Expand Down Expand Up @@ -33,4 +38,8 @@ jobs:
with:
app_id: apius_lang_entropy
version: ${{ needs.version.outputs.version }}
# Splunkbase listing id (repo variable). Empty -> Splunkbase publish is
# skipped by the reusable workflow; the manual approval gate lives in the
# `splunkbase` Environment.
splunkbase_app_id: ${{ vars.SPLUNKBASE_APP_ID }}
secrets: inherit
Loading