ansible: update gh-bot server#3803
Merged
richardlau merged 1 commit intonodejs:mainfrom Jul 5, 2024
Merged
Conversation
Create a new Debian 12 server to replace the Debian 8 `gh-bot` server. Update the `ansible/playbooks/create-github-bot.yml` playbook to automate setup, including: - Fetching of deployment secrets from the secrets repository. - Generating the allowlist of `jenkins-workspace` IP addresses from the inventory. - Restarting the services if required.
targos
approved these changes
Jul 4, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Create a new Debian 12 server to replace the Debian 8
gh-botserver. Update theansible/playbooks/create-github-bot.ymlplaybook to automate setup, including:jenkins-workspaceIP addresses from the inventory.Fixes: #3214
This is deployed to the new server and I've updated the DNS entry for the bot in CloudFlare to the new IP address.
We can remove the old server once we're happy the new one is operating without issues (or if we do find issues we can swap the DNS entry back to the old IP address).