approle: do not require secret_id

[fairclothjm]

Description

secretId is no longer required for approle to support advanced use cases like machine login when bind_secret_id is false.

Closes #520

Checklist

• Added CHANGELOG entry (only for user-facing changes)
• Did not commit changes to dist/index.js (This is only done for releases by vault-action maintainers)

Community Note

• Please vote on this pull request by adding a 👍
  reaction
  to the original pull request comment to help the community and maintainers
  prioritize this request
• Please do not leave "+1" comments, they generate extra noise for pull request
  followers and do not help prioritize the request

[madAndroid]

This doesn't appear to be working exactly as intended - I realise this change isn't released yet, but shouldn't I be able to use this by pointing my pipelines at @main?

Here's my action yaml:

jobs:
  create-bundle:
    name: Prepare and upload support bundle
    runs-on: my-custom-runner
    steps:

      - name: Import Secrets
        id: import-secrets
        uses: hashicorp/vault-action@main
        with:
          url: 'https://[REDACTED]'
          method: approle
          namespace: [REDACTED]
          roleId: ${{ secrets.VAULT_ROLE_ID }}
          secrets: |
            foo/data/foo username | FOO_USERNAME ;
            bar/data/bar password | BAR_PASSWORD

In my ARC runner pods, I see the correct git sha being downloaded, but it fails with:

Error: Input required and not supplied: secretId