jfrog / jfrog/setup-jfrog-cli

Allow oidc-user to be marked as non secret for CI

Open
#207 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
TypeScript
Stars
266
Forks
110
Avg merge
3d 15h
Merged PRs (30d)
3

Description

Is your feature request related to a problem? Please describe.

this action currently has two outputs

outputs:
oidc-token:
description: "JFrog OIDC token generated by the Setup JFrog CLI when setting oidc-provider-name."
oidc-user:
description: "JFrog OIDC username from the OIDC token generated by the Setup JFrog CLI when setting oidc-provider-name."

the latter would useful for troubleshooting action pipelines, however it is by default marked a secret and therefore not easily consumed for informational purposes.
It would be great if there was an optional input argument to mark this output as non secret so it could be used for various purposes within the CI

Describe the solution you'd like to see

Something to the effect of

inputs:
mask-oidc-user:
description: "Mask OIDC User"
default: true
required: false

and naturally some update to the internal JS code to propagate this boolean to the github sdk when adding the output such that it's not set as a secret

Describe alternatives you've considered

No response

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the action metadata that declares oidc-user and the TypeScript entry point that adds it as an output; trace how the requested boolean reaches the GitHub SDK. Done means an optional default-true mask-oidc-user input controls whether oidc-user is marked secret, with coverage for both settings.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, typescript
Domain
ci-cd, devops
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.