Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request - instructions for usage on GitHub Actions #79

Open
bradymholt opened this issue Nov 17, 2022 · 1 comment
Open

Feature request - instructions for usage on GitHub Actions #79

bradymholt opened this issue Nov 17, 2022 · 1 comment
Assignees

Comments

@bradymholt
Copy link

When experimenting with using this CLI on GitHub Actions I experienced a very long install time using the homebrew approach on a Linux based runner. It was taking about 4.5m to install the CLI. I'm not sure that the bottleneck is there but I was able to download one of the releases directly and it was much faster (see below).

I think adding something to the README (or other documentation) about usage within GitHub Actions could be helpful as this is an increasingly popular platform for workflow automatations.

Here are the steps I used to get the CLI installed and authenticated quickly

- name: Provision cb CLI
  run: |
    curl --silent --location "$(curl --silent https://api.github.com/repos/CrunchyData/bridge-cli/releases/latest | jq -r '.assets[].browser_download_url | select(test("cb-v1.3.0_linux_amd64.zip"))')" -o cb.zip
    unzip ./cb.zip && rm ./cb.zip && sudo mv ./cb /usr/local/bin
    mkdir -p $HOME/.config/cb
    echo "$CRUNCHY_BRIDGE_AUTH" > $HOME/.config/cb/api.crunchybridge.com
  env:
    CRUNCHY_BRIDGE_AUTH: ${secrets.CRUNCHY_BRIDGE_AUTH}
- name: Run cb whoami command
   run: cb whoami
@abrightwell abrightwell self-assigned this Nov 18, 2022
@abrightwell
Copy link
Member

Thanks for the feedback! I'll start looking into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants