conda activate fails with CommandNotFoundError

[skwde]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.73.1 (commit: 6261075)
• OS Version: macOS BigSur (11.7)

Steps to Reproduce: (I also asked this here: https://stackoverflow.com/questions/74569128/use-conda-envrionment-in-vscode-task, but I didn't got a reply)

0. Install conda (https://docs.conda.io/projects/conda/en/latest/user-guide/install/download.html) and ensure that conda is in your PATH
1. Create conda environment via conda env create -n mkdocs python=3 mkdocs-material; Ensure that you can activate the environment conda activate mkdcos
2. Create following following tasks

{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "conda info",
      "type": "shell",
      "command": "type conda; which conda",
    },
    {
      "label": "Activate conda envrionment: mkdocs",
      "type": "shell",
      "command": "conda",
      "args": [
        "activate", "mkdocs"
      ]
    },
    {
      "label": "Serve mkdocs",
      "type": "shell",
      "command": "mkdocs serve --strict --dev-addr localhost:8010",
    },
    {
      "label": "run mkdocs serve in environment",
      "group": "test",
      "presentation": {
        "reveal": "always",
        "panel": "shared"
      },
      "runOptions": { 
        "runOn": "folderOpen" 
      },
      "dependsOrder": "sequence",
      "dependsOn": [
        "conda info",
        "Activate conda envrionment: mkdocs", 
        "Serve mkdocs"
      ],
    }
  ]
}

3. Run the task and see that it fails with

CommandNotFoundError: Your shell has not been properly configured to use 'conda activate'.

Note, I have "python.condaPath" set and conda info / which conda tasks shows the correct path. Moreover when I open a terminal in VScode I can just execute the command and it works.

[meganrogge]

This is an environment issue bc tasks is likely running the rc file instead of the profile. I'd try adding conda to the path for both

[skwde]

I don't quite get why this is closed. How can it be an environment issue when conda can be used outside of tasks without an issue and which conda or conda info is showing the correct path when run as a task?