Skip to content

Pass secrets to reusable workflow for Maven SNAPSHOT deployment#248

Merged
dkayiwa merged 1 commit intomasterfrom
fix/pass-secrets-to-reusable-workflow
Mar 9, 2026
Merged

Pass secrets to reusable workflow for Maven SNAPSHOT deployment#248
dkayiwa merged 1 commit intomasterfrom
fix/pass-secrets-to-reusable-workflow

Conversation

@dkayiwa
Copy link
Member

@dkayiwa dkayiwa commented Mar 9, 2026

Problem

The CI build (run #497) fails during the Maven deploy step with a 401 Unauthorized error because MAVEN_REPO_USERNAME and MAVEN_REPO_API_KEY are empty.

The reusable workflow build-backend-module.yml expects these secrets to authenticate with the OpenMRS Maven snapshot repository, but maven.yml was not forwarding any secrets.

Fix

Add secrets: inherit to pass organization-level secrets to the reusable workflow.

The deploy step in the shared build-backend-module workflow needs
MAVEN_REPO_USERNAME and MAVEN_REPO_API_KEY secrets to authenticate
with the OpenMRS Maven snapshot repository. Explicitly pass only the
three required secrets (NVD_API_KEY, MAVEN_REPO_USERNAME,
MAVEN_REPO_API_KEY) to follow the convention used by other OpenMRS
modules like webservices.rest and emrapi.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@dkayiwa dkayiwa force-pushed the fix/pass-secrets-to-reusable-workflow branch from 6b2917e to 2986258 Compare March 9, 2026 22:55
@dkayiwa dkayiwa merged commit 3b1361e into master Mar 9, 2026
3 checks 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