This is just a warning which shouldn’t affect anything. If you aren’t running trellis init then that means you’re managing dependencies (like Ansible) yourself and presumably it worked before as you said.
That’s coming from Ansible and the deploy playbook; nothing related to trellis-cli which just invokes ansible-playbook.
But I’m assuming that’s the actual issue here since that’s an interactive prompt and it won’t get any input so it fails.
repo_accept_hostkey: true doesn’t matter here either. That’s for when git is cloning your repo on the remote server but the deploy is failing well before then. It’s failing trying to SSH from CircleCI to your staging server as the web user.
This is an SSH client issue on CircleCI. This means you need to configure CircleCI to accept your staging’s server as a known host.
The thought had occurred to me, so yeah can definitely do that.
What’s the folder structure for your repo look like? I realize I definitely wrote this workflow assuming the standard one, so it might need an option to set the site/trellis dir. The 3 steps that use trellis-cli at the bottom need a working-directory set in non-standard cases.
One of my first deploy attempts showed this in GH Actions:
Initializing the repository
/usr/bin/git init /home/runner/work/*project_name*/*project_name*
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint: git config --global init.defaultBranch <name>
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint: git branch -m <name>
Initialized empty Git repository in /home/runner/work/*project_name*/*project_name*/.git/
/usr/bin/git remote add origin https://github.com/*my_org_profile*/*project_name*
In fact when I added working-directory: trellis/ to forked ver of your repo it make it work.