Running conda init remotely via Ansible in order to configure bash to load with base environment enabled by default?

I am setting up a playbook that will set up an environment using the Miniforge3 conda flavour.

So far I have the following:

---

- hosts: all
  become: true
  tasks:
    - name: Download miniforge mamba
      shell:
        cmd: |
          curl -L -O "https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-$(uname)-$(uname -m).sh"
    - name: Run miniforge mamba
      shell:
        cmd: |
          bash Miniforge3-$(uname)-$(uname -m).sh -p /opt/miniforge3/ -b
          /opt/miniforge3/bin/conda init

The first task runs without any issues. The second though, while not emitting any errors, appears to only complete the installation but does not initialize conda in .bashrc.

If I run the two commands in SSH session manually, I get the desired result – a modified .bashrc with the base environment activated.

I noticed the same issue with Micromamba but I thought it was that flavour at fault (the installation instructions do need some polishing imho).