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

Is there a way to specify ARCH type for pulling the right binaries for the setup tools #47

Closed
00r2 opened this issue Jan 12, 2024 · 5 comments

Comments

@00r2
Copy link

00r2 commented Jan 12, 2024

I am using this action quite often and recently we adopted ARM based runners and the setup tools is failing to pull the arm based binaries. Is there anyway to provide an input to select architecture type like (amd64 or arm64) etc?

@yokawasa
Copy link
Owner

yokawasa commented Feb 18, 2024

@00r2 thank you for your opening issue and I'm very sorrry for the late response.

I think I can add new arch-type parameter like this below. would it work for you?

Suppose that new input parameter named arch-type ('amd64' by default) is added
Sample workflow would be like this

  test: 
    steps:
    - uses: actions/checkout@v4
    - uses: yokawasa/[email protected]
      with:
        arch-type: 'arm64'
        setup-tools: |
          kubectl
        kubectl: '1.25'
    - run: |
        kubectl version --client

@00r2
Copy link
Author

00r2 commented Feb 20, 2024

Thank you @yokawasa 🙏That will be perfect.

@yokawasa
Copy link
Owner

@00r2 v0.11.0 has been released. you can specify archi-type with v0.11.0

https://github.com/yokawasa/action-setup-kube-tools/releases/tag/v0.11.0

@00r2
Copy link
Author

00r2 commented Feb 24, 2024

Thank you 🙏 @yokawasa i will give this a try. Appreciate you getting this out quickly 😊

@yokawasa
Copy link
Owner

@00r2 I'm closing this issue. please open another issue if you have any problems or request 🙏

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