Skip to content

fix: configure OpenAPI publisher app client ID #19

Description

@lusu007

Problem

service-moderation cannot publish its generated OpenAPI snapshot because it does not have the GitHub App credentials required by the reusable publisher workflow.

The source service successfully generates, validates, and uploads openapi.json. The reusable publish-openapi-snapshot.yml workflow then fails in actions/create-github-app-token@v3 before checking out groundsgg/api-reference:

The 'client-id' (or deprecated 'app-id') input must be set to a non-empty string.

This reproduced on both published service-moderation releases:

Confirmed comparison

service-permissions uses the same caller shape and the same reusable workflow successfully:

service-moderation currently has neither OPENAPI_PUBLISHER_APP_ID nor OPENAPI_PUBLISHER_PRIVATE_KEY; its only repository secret is RELEASE_PLEASE_TOKEN. The action validates the empty App ID first, so the missing private key is not reached yet.

Expected outcome

  • Prefer centrally managed organization variable and secret visibility for every approved OpenAPI-producing service, including service-permissions and service-moderation; alternatively configure the two credentials repository-locally for moderation.
  • Use the non-deprecated client-id action input in the reusable workflow.
  • Re-run the failed v0.1.1 publication successfully.
  • Confirm the snapshot PR is created or updated in groundsgg/api-reference.

No application image or moderation runtime deployment is blocked by this documentation-publication failure.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions