jfrog / jfrog/setup-jfrog-cli

OIDC-only mode that doesn’t install jfrog CLI

Open
#209 4 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.

We are using this action to authenticate with OIDC to jfrog’s servers.
We don’t use jfrogs cli tools but our own tooling (docker, conda, pixi, …)
Would it be possible to skip the download + configure cli parts and only do the OIDC auth in this action and skip all of the additional jf setup?

Describe the solution you'd like to see
- uses: jfrog/setup-jfrog-cli@v4
  id: artifactory
  with:
    oidc-provider-name: ${{ vars.ARTIFACTORY_OIDC_PROVIDER }}
    oidc-audience: ${{ vars.ARTIFACTORY_OIDC_AUDIENCE }}
    oidc-only: true
  env:
    JF_URL: ${{ vars.ARTIFACTORY_URL }}
- uses: prefix-dev/setup-pixi@v0.8.1
  with:
    auth-host: ${{ vars.ARTIFACTORY_URL }}
    auth-username: ${{ steps.artifactory.outputs.oidc-user }}
    auth-password: ${{ steps.artifactory.outputs.oidc-token }}
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 at the action entry point and trace the existing OIDC authentication and CLI setup flow; no file or test is identified in the issue. Confirm how inputs and outputs are exposed, then define done as an oidc-only input that returns the OIDC user and token while skipping JFrog CLI download and configuration, with existing behavior unchanged.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.