Content is not a valid JSON object

Similar to #5, I created a service principal and got the result of

{
  "clientId": "<GUID>",
  "clientSecret": "<GUID>",
  "subscriptionId": "<GUID>",
  "tenantId": "<GUID>",
  "activeDirectoryEndpointUrl": "https://login.microsoftonline.com",
  "resourceManagerEndpointUrl": "https://management.azure.com/",
  "activeDirectoryGraphResourceId": "https://graph.windows.net/",
  "sqlManagementEndpointUrl": "https://management.core.windows.net:8443/",
  "galleryEndpointUrl": "https://gallery.azure.com/",
  "managementEndpointUrl": "https://management.core.windows.net/"
}

However, I got the following error when I login to Azure:

Content is not a valid JSON object

I omitted, just in case, unnecessary properties from the JSON object like:

{
  "clientId": "<GUID>",
  "clientSecret": "<GUID>",
  "subscriptionId": "<GUID>",
  "tenantId": "<GUID>"
}

And the result is still the same. What am I missing?

[aksm-ms]

@justinyoo Please update your workflow as follows:

• name: Login to Azure uses: Azure/login@v1 env: CREDENTIALS: ${{ secrets.AZURE_CREDENTIALS }} with: creds: ${{ env.CREDENTIALS }}

Reference - https://docs.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#env-context

[justinyoo]

I found why I got the error. Here’s my action:

- name: Login to Azure
  uses: Azure/login@v1
  env:
    CREDENTIALS: ${{ secrets.AZURE_CREDENTIALS }}
  with:
    creds: $CREDENTIALS

I intentionally used the environment variable at the step level. However, it didn’t pass to the parameter. Can we use the environment variable to capture secrets from the repo?