This worked fine up until last night, but now we experience the problem that the ‘SSH Permission’ key we’ve added, is not injected anymore.
defaults: &defaults docker: - image: registry.ours.com/buildcontainer auth: username: xx password: xx # also tried '2.0', '2' version: 2.1 jobs: deploy: <<: *defaults steps: - add_ssh_keys: fingerprints: - "xx:...:xx" - checkout - run: name: deploy command: | ssh -T firstname.lastname@example.org
Goes without saying; the fingerprint is the same value as the fingerprint displayed in SSH Permission.
It used to work fine, even without the ‘add_ssh_keys’ (version: 2). If we take and old project and click rebuild, we still get the behaviour from before: The ssh -T command shows the full list of what we have access to through that fingerprint key. If we remove it, and rebuild, we see that the access drops.
However, if we do the same for a new project this doesn’t work anymore (maybe since last night, definitely since this morning). It only wants to use the ‘CircleCI Deploy Key’ that is added
automatically and is registered in the (bitbucket) repo.
Is anyone experiencing something similar since the last day or so ?
Any thoughts on what we can try ? We’ve already tried with multiple repo’s, copying the files and config.yaml script that worked for the ‘old’ rebuild triggers to newly created repo’s, …
Nothing seems to work anymore.
Any help is much appreciated.