data.coop/ansible
8
3
Fork 7
Code Issues 52 Pull requests 10 Projects 1 Releases Wiki Activity

Use become #116

Closed
reynir wants to merge 1 commit from become into main
pull from: become
merge into: data.coop:main
Conversation 8 Commits 1 Files changed 2 +2 -2
reynir commented 2022-11-16 12:49:46 +00:00
Owner
Copy link

We don't setup ssh keys for root anymore.

We don't setup ssh keys for root anymore.
reynir added 1 commit 2022-11-16 12:49:46 +00:00 
We don't setup ssh keys for root anymore.
samsapti commented 2022-11-16 13:11:14 +00:00
Owner
Copy link

How would we not use the root user on the first run, when our users don't exist yet?

How would we not use the root user on the first run, when our users don't exist yet?
samsapti commented 2022-11-16 13:16:47 +00:00
Owner
Copy link

It wouldn't work with Vagrant, because our users don't exist yet.

It wouldn't work with Vagrant, because our users don't exist yet.
samsapti commented 2022-11-16 13:50:58 +00:00
Owner
Copy link

Also,

We don't setup ssh keys for root anymore.

Yes we do. But maybe we shouldn't? In Vagrant the default user is named vagrant, and it has an empty password. But in production, which user should the initial SSH session use? Or maybe I'm overdoing the reproducability thingy, I don't know :D

Also, > We don't setup ssh keys for root anymore. Yes we do. But maybe we shouldn't? In Vagrant the default user is named `vagrant`, and it has an empty password. But in production, which user should the initial SSH session use? Or maybe I'm overdoing the reproducability thingy, I don't know :D
reynir commented 2022-11-16 15:05:39 +00:00
Author
Owner
Copy link

Also,

We don't setup ssh keys for root anymore.

Yes we do.

Oh. I thought #35 was merged. In any case, at the moment only your key is in root's authorized_keys :D

> Also, > > > We don't setup ssh keys for root anymore. > > Yes we do. Oh. I thought https://git.data.coop/data.coop/ansible/pulls/35 was merged. In any case, at the moment only your key is in root's authorized_keys :D
😕 1
valberg commented 2022-11-16 18:16:14 +00:00
Owner
Copy link

@reynir can we close this since #120 has been merged?

@reynir can we close this since #120 has been merged?
reynir commented 2022-11-16 18:24:01 +00:00
Author
Owner
Copy link

Hmm, yes, it's not needed now. With #35 we probably need it again. I'm not sure why #34 was closed when #35 has not been merged :-)

Hmm, yes, it's not needed *now*. With https://git.data.coop/data.coop/ansible/pulls/35 we probably need it again. I'm not sure why https://git.data.coop/data.coop/ansible/issues/34 was closed when #35 has not been merged :-)
reynir commented 2022-11-16 18:24:24 +00:00
Author
Owner
Copy link

We can come back to this when it becomes relevant.

We can come back to this when it becomes relevant.
reynir closed this pull request 2022-11-16 18:24:24 +00:00
valberg commented 2022-11-16 18:27:25 +00:00
Owner
Copy link

Hmm, yes, it's not needed now. With #35 we probably need it again. I'm not sure why #34 was closed when #35 has not been merged :-)

Oh, that is a good question. I can't answer it and I closed it 🤣

> Hmm, yes, it's not needed *now*. With https://git.data.coop/data.coop/ansible/pulls/35 we probably need it again. I'm not sure why https://git.data.coop/data.coop/ansible/issues/34 was closed when #35 has not been merged :-) Oh, that is a good question. I can't answer it and I closed it 🤣
😆 1

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
Blocked

Something is blocking progress

  
Existing Service

Issues/improvements regarding existing services

  
Infrastructure Issue

Infrastructure issue that needs investigation or time to fix

  
Refactor

Refactoring of files / file structure or other improvements

  
Security Hardening

Non-verified / non-critical security improvements

  
Security Issue

Urgent security issue that needs to be fixed ASAP

  
Service Idea

Ideas for new services

  
Service Removal

Removal of services for one reason or another

  
Upgrade service
No labels
Blocked
Existing Service
Infrastructure Issue
Refactor
Security Hardening
Security Issue
Service Idea
Service Removal
Upgrade service
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: data.coop/ansible#116
No description provided.
Delete branch "become"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?