Describe the solution you'd like
ArgoCD self-hosts artifacts for the CLI on it's web server. As a user, I'd like to be able to configure this action to download whatever version my self-hosted Argo is currently providing, for a few reasons:

• To keep my CD instance and the CLI in-sync automatically
• To avoid GH rate limiting when downloading artifacts

I have a Github Actions workflow set up that creates an appset as described in the documentation: https://argo-cd.readthedocs.io/en/stable/user-guide/commands/argocd_appset/

When I run my workflow, I see this step fails

      - name: "Create AppSet"
        uses: clowdhaus/argo-cd-action/@main
        env:
          ARGOCD_SERVER: some.server
        with:
          command: appset create app.yaml

with this error description:

/opt/hostedtoolcache/argocd/2.6.7/x64/argocd appset create app.yaml
time="2023-08-02T20:42:08Z" level=fatal msg="rpc error: code = Unimplemented desc = unknown service applicationset.ApplicationSetService"
Error: The process '/opt/hostedtoolcache/argocd/2.6.7/x64/argocd' failed with exit code 20

unknown service applicationset.ApplicationSetService sounds like ArgoCD AppSets are not supported, is that correct?

Hello im trying to use this action for patching a resource and is not working , i tried with many options out there and always remove the simple quote '

    - name: Replacing..
      run: |
        CMD="patch-resource apps-account-activation-frontend-${{github.event.inputs.Environment}} --kind ${{github.event.inputs.Type}} --patch '{"spec": {"replicas": ${{github.event.inputs.UpDownScale}}}}'"
        echo $CMD
        echo "CMD="patch-resource apps-account-activation-frontend-${{github.event.inputs.Environment}} --kind ${{github.event.inputs.Type}} --patch '{"spec": {"replicas": ${{github.event.inputs.UpDownScale}}}}'"" >> $GITHUB_ENV
        
    - uses: clowdhaus/argo-cd-action/@main
      name: ArgoCd Scale to ${{github.event.inputs.UpDownScale}} 
      with:
        command: app
        options: '${{env.CMD}}'

output

/home/runner/_work/_tool/argocd/2.3.3/x64/argocd app patch-resource apps-account-activation-frontend-qa5 --kind Deployment --patch {"spec": {"replicas": 2}}
Patch resource in an application

Describe the bug
The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files.

To Reproduce

- name: Login to ArgoCD
   uses: clowdhaus/argo-cd-action/@main
   with:
     version: ${{ env.ARGOCD_VERSION }}
     command: login
     options: >-
       ${{ secrets.ARGOCD_URL }}
        --username ${{ secrets.ARGOCD_USERNAME }}
        --password ${{ secrets.ARGOCD_PASSWORD }}
        --grpc-web

It seems to be

Expected behavior
No warnings when using the action

Additional context
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

actions/toolkit#1218
actions/toolkit#1178

Describe the bug
A clear and concise description of what the bug is.
Using argo-cd-action/v1.15.0, argo-cd-action/v1.17.0, ArgoCD workflow gets stuck at App Sync stage indefinitely.
ArgoCD server version: v2.5.1+504da42

To Reproduce
Steps to reproduce the behavior:

• name: Argocd app sync
  uses: clowdhaus/argo-cd-action/@v1.17.0
  with:
  version: 2.5.1
  command: app sync ${{ env.PARENT_APP_NAME }} -l argocd.argoproj.io/instance=${{ env.PARENT_APP_NAME }}
  options: --auth-token=${{ secrets.ARGOCD_AUTH_TOKEN }} --server ${{ env.ARGOCD_SERVER }}

Problem

The ArgoCD cli CPU architecture is hardcoded to amd64.
It is not possible to use other architectures although the official CLI is also built for them.

Proposed solution

Take into consideration the CPU architecture of the runner when fetching the argocd binary.

Describe the bug
We were using clowdhaus/argo-cd-action/@main for GHA but today our pipelines started to fail - we use node
They work fine for v1.4.2 version but we are using nodejs in version 12.

Expected behavior
Should be backward compatible/breaking changes should be annoucned.

Additional context
NodeJS 12 & 14

Is your feature request related to a problem? Please describe.
Supply chain injections are becoming a common security flaw in CI systems and build chains. This includes:

• squatting in typo-named repos
• where CI tools can be compromised, pushing tags/releases that masquerade as official ones
• where repos have been renamed, or changed ownership, squatting in a previous repository name

Describe the solution you'd like

ArgoCD provides multiple mechanisms to validate the authenticity of the download, with SLSA and weaker SHA256 checksums available. Using one of these to verify the provenance of the intended version improves the integrity of using the dependancy.

This would be in the code to download ArgoCD for use by this action.

Using the SLSA method is preferred as it is more secure.

Describe alternatives you've considered
Using the simpler SHA256 mechanism. Performing these actions without using this repository.

Additional context
Add any other context or screenshots about the feature request here.

Describe the bug
When I first introduced this action it worked fine. However on subsequent runs it fails. I'm using a self-hosted runner without a specific clean-up step.

To Reproduce
Steps to reproduce the behavior:

1. Create a workflow with this action
2. Run it and see it works
3. Run it again and it will fail with

Unexpected error attempting to determine if executable file exists '/home/github/_work/_tool/argocd/2.0.0/x64/argocd/argocd': Error: ENOTDIR: not a directory, stat '/home/github/_work/_tool/argocd/2.0.0/x64/argocd/argocd'
Error: Unable to locate executable file: argocd. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.

Expected behavior
I expected the action to be succesful every time.

Additional context
The argocd file is located /home/github/_work/_tool/argocd/2.0.0/x64/argocd, so the mechanism to find already downloaded executable is searching with a path that is too long.

Describe the bug
When running argo-cd-action on a custom runner, steps fail if the /home/actions/argocd directory already exists

To Reproduce
Steps to reproduce the behavior:

1. Add [email protected] to a project that uses a custom runner and has previously used argo-cd-action v1.12.1
2. Run an argocd command
3. Get an error. that the /home/actions/argocd directory already exists

Debug Log

##[debug][index] command: app,sync,foo,-l,argocd.argoproj.io/instance=bar
##[debug][index] options: --auth-token=***
##[debug][index] version: 2.8.4
##[debug]isExplicit: 2.8.4
##[debug]explicit? true
##[debug]checking cache: /home/actions/_work/_tool/argocd/2.8.4/x64
##[debug]not found
##[debug]Unable to find "argocd" executable, downloading it now
##[debug][debug()] getExecutableUrl: https://github.com/argoproj/argo-cd/releases/download/v2.8.4/argocd-linux-amd64
##[debug]Downloading https://github.com/argoproj/argo-cd/releases/download/v2.8.4/argocd-linux-amd64
##[debug]Destination /home/actions/argocd
Destination file path /home/actions/argocd already exists
Waiting 16 seconds before trying again
Destination file path /home/actions/argocd already exists
Waiting 17 seconds before trying again
Error: Destination file path /home/actions/argocd already exists

Describe the bug
v1.9.0 fails to run.

Our workflow is set up like the documentation instructs instruct: uses: clowdhaus/argo-cd-action@main, which will use latest version. However the workflow startet to fail today, and I can see that v1.9.0 was released yesterday.

Run clowdhaus/argo-cd-action@main
Destination file path /home/github/argocd already exists
Waiting 17 seconds before trying again
Destination file path /home/github/argocd already exists
Waiting 16 seconds before trying again
Error: Destination file path /home/github/argocd already exists

To Reproduce
Steps to reproduce the behavior:

1. set up a workflow that uses this action
2. run it multiple times and it should fail on subsequent runs

Expected behavior
The script will execute as usual, without errors

Screenshots

Additional context
Running as a github runner on a selfhosted runner using https://github.com/SanderKnape/github-runner