Skip to content

Commit bf9644a

Browse files
Fix setup-jfrog: remove poetry config calls that run before poetry install
The composite action runs before Poetry is installed, so poetry commands fail with "command not found". Keep only PIP_INDEX_URL which Poetry's pip-based installer respects (matching databricks-sql-python2 pattern). Co-authored-by: Isaac Signed-off-by: Vikrant Puppala <vikrant.puppala@databricks.com>
1 parent 5ff9142 commit bf9644a

1 file changed

Lines changed: 3 additions & 10 deletions

File tree

.github/actions/setup-jfrog/action.yml

Lines changed: 3 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
name: Setup JFrog OIDC
2-
description: Obtain a JFrog access token via GitHub OIDC and configure pip/Poetry to use JFrog PyPI proxy
2+
description: Obtain a JFrog access token via GitHub OIDC and configure pip to use JFrog PyPI proxy
33

44
runs:
55
using: composite
@@ -24,16 +24,9 @@ runs:
2424
echo "JFROG_ACCESS_TOKEN=${ACCESS_TOKEN}" >> "$GITHUB_ENV"
2525
echo "JFrog OIDC token obtained successfully"
2626
27-
- name: Configure pip and Poetry
27+
- name: Configure pip
2828
shell: bash
2929
run: |
3030
set -euo pipefail
31-
32-
# Configure pip index (used by Poetry's installer under the hood)
3331
echo "PIP_INDEX_URL=https://gha-service-account:${JFROG_ACCESS_TOKEN}@databricks.jfrog.io/artifactory/api/pypi/db-pypi/simple" >> "$GITHUB_ENV"
34-
35-
# Configure JFrog as a supplemental source for Poetry
36-
poetry config repositories.jfrog https://databricks.jfrog.io/artifactory/api/pypi/db-pypi/simple
37-
poetry config http-basic.jfrog gha-service-account "${JFROG_ACCESS_TOKEN}"
38-
39-
echo "pip and Poetry configured to use JFrog registry"
32+
echo "pip configured to use JFrog registry"

0 commit comments

Comments
 (0)