kyma-project / kyma-project/setup-kyma-cli

Missing variables in output

Open Beginner friendly
#33 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
No language data
Stars
1
Forks
5
PR merge metrics
No merged PRs in 30d

Description

Description

When testing the workflow for a scenario when we try to download the Kyma CLI providing the open-source / github.com token, I've stumbled upon a message with some missing variables:

Image

This only happens when the setup-kyma-cli action is referenced by a repository, i.e. when used uses: kyma-project/setup-kyma-cli@v1 and not uses: ./.

Sample outputs:

  1. How it should look like: https://github.tools.sap/otters/cli-test-examples/actions/runs/30068174/job/142141311#step:4:181
  2. How it looks like: https://github.tools.sap/otters/cli-test-examples/actions/runs/30068174/job/142141311#step:4:116

The place in code looks as follows:

echo "Installed $(${TARGET_PATH} version) to $(readlink -f "${TARGET_PATH}")"

The TARGET_PATH is used twice and it works for the second time so there's something wrong with the $(${TARGET_PATH} version) part.

Expected result

The output for both the local workflow and reference workflow should behave the same.

Actual result

It's different.

Steps to reproduce

Try running the workflow in the cli-test-example repo
https://github.tools.sap/otters/cli-test-examples/actions/runs/29911175/job/141434146#step:4:116

Troubleshooting

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 with the shell step containing echo "Installed $(${TARGET_PATH} version) to $(readlink -f "${TARGET_PATH}")" and compare its behavior when the action is referenced with uses: kyma-project/setup-kyma-cli@v1 versus uses: ./. Reproduce the workflow from the linked cli-test-examples run. Done means both workflows produce equivalent output with the installed version and path shown.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, shell
Domain
ci-cd, devops
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
76/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.