Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(argo-cd): Add new BitbucketCloud ssh keys in values.yaml #2062

Merged

Conversation

jdvgh
Copy link
Contributor

@jdvgh jdvgh commented May 17, 2023

Closes #2059

Checklist:

  • I have bumped the chart version according to versioning
  • I have updated the documentation according to documentation
  • I have updated the chart changelog with all the changes that come with this pull request according to changelog.
  • Any new values are backwards compatible and/or have sensible default.
  • I have signed off all my commits as required by DCO.
  • My build is green (troubleshooting builds).

@jdvgh jdvgh changed the title feat: Add new BitbucketCloud ssh keys feat(argo-cd): Add new BitbucketCloud ssh keys May 17, 2023
@jdvgh jdvgh changed the title feat(argo-cd): Add new BitbucketCloud ssh keys feat(argo-cd): Add new BitbucketCloud ssh keys in values.yaml May 17, 2023
@jdvgh jdvgh force-pushed the argo-cd-update-bitbucket-cloud-new-ssh-keys branch from bc48bd5 to 1258929 Compare May 17, 2023 13:00
Update configs.ssh.kownHosts in charts/argo-cd/values.yaml to match new SSHKeys from https://bitbucket.org/site/ssh (as of May 17th, 2023)

Signed-off-by: jdvgh <133217951+jdvgh@users.noreply.github.com>
@jdvgh jdvgh force-pushed the argo-cd-update-bitbucket-cloud-new-ssh-keys branch from 1258929 to f02715d Compare May 17, 2023 13:57
@jdvgh jdvgh marked this pull request as ready for review May 17, 2023 14:04
@@ -315,6 +315,8 @@ configs:
# -- Known hosts to be added to the known host list by default.
# @default -- See [values.yaml]
knownHosts: |
bitbucket.org ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIIazEu89wgQZ4bqs3d63QSMzYVa0MuJ2e2gKTKqu+UUO
bitbucket.org ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBPIQmuzMBuKdWeF4+a2sjSSpBK0iqitSQ+5BM9KhpexuGt20JpTVM7u5BDZngncgrqDMbWdxMWWOGtZ9UgbqgZE=
bitbucket.org ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAubiN81eDcafrgMeLzaFPsw2kNvEcqTKl/VqLat/MaB33pZy0y3rJZtnqwR2qOOvbwKZYKiEO1O6VqNEBxKvJJelCq0dTXWT5pbO2gDXC6h6QDXCaHo6pOHGPUy+YBaGQRGuSusMEASYiWunYN0vCAI8QaXnWMXNMdFP3jHAJH0eDsoiGnLPBlBp4TNm6rYI74nMzgz3B9IikW4WVK+dc8KZJZWYjAuORU3jc1c/NPskD2ASinf8v3xnfXeukU0sJ5N6m5E8VLjObPEO+mN2t/FZTMZLiFqPWc/ALSqnMnnhwrNi2rbfg/rd/IpL8Le3pSBne8+seeFVBoGqzHM9yXw==
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As of https://bitbucket.org/site/ssh
The ssh-rsa key is still valid; So I kept it

@jmeridth jmeridth merged commit 7347a5d into argoproj:main May 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bitbucket ssh host key change
3 participants