I have a Bamboo deploy plan that I'm updating to point to a new host - SCP and SSH tasks that previously logged into one host now login to another.
The old host allowed a username/password login. The new only allows SSH key-based authentication.
I have update the spec to use the new host IP and shared credentials. However, after pushing changes and confirming the spec was scanned, I see these tasks pointing to the new IP, but still using the old username.
From this, I can tell the commit to the spec repo is correctly scanned and the plan is being updated accordingly; it's as if credentials are cached somewhere, untouched by this update.
How can I resolve this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.