What to do if I run playbook again after disabling root in Ansible?

How can I maintain 等 equality if I first add a deploy user to the root user and prohibit logging in as root in the following configuration?
The first time a command like ansible-playbook-istaging site.yml works fine, but the second time you can't log in with root, so you get an error.In this case, I think there are many ways to do it (e.g., --limit after separating files), but what is the best way to do it?

-hosts:webservers
  remote_user —root
  port —22
  Roles:
    - something1

- hosts —webservers
  remote_user:deploy
  port —10022
  Roles:
    - something 2

ansible

2022-09-30 16:23

1 Answers

Basically, I think it's good to have the playbook run as a deploy user and only as a root user at the beginning.

---
- hosts —webservers
  remote_user:deploy
  become:yes
  port —10022
  tags: ['init']
  Roles:
  - useradd_deploy
  - disable_root_user
  - sshd

- hosts —webservers
  remote_user:deploy
  port —10022
  Roles:
  - something 2

The first time is root, port 22 and init tag only

$ansible-playbook-i hosts site.yml --tags init-eansable_ssh_user=root-eansable_ssh_port=22

After the second time, I'll keep playingbook

$ansable-playbook-i hosts site.yml

After the second time, the init tag will be played, but I think there will be no problem if the 等 equality is ensured.
However, deploy users need to set sudoers in init play…

(If the order of init is wrong, no one will be able to log in remotely.)

2022-09-30 16:23

If you have any answers or tips

Popular Tags

python x 4647

android x 1593

java x 1494

javascript x 1427

c x 927

c++ x 878

ruby-on-rails x 696

php x 692

python3 x 685

html x 656