Try to correct chicken-or-egg problem with users and DB properties #135
Conversation
|
@geerlingguy this CentOS 8 issue seems to be unrelated to my change - could we rerun the CI? |
|
This pull request has been marked 'stale' due to lack of recent activity. If there is no further activity, the PR will be closed in another 30 days. Thank you for your contribution! Please read this blog post to see the reasons why I mark pull requests as stale. |
|
@geerlingguy Do you mind to have a look at this PR before the stale bot will close this. |
|
This issue is no longer marked for closure. |
|
Any news on this? I'm still using this role directly pulled from github with this patch applied to fulfill our needs, but I'd love to switch back to the official ansible galaxy version. @geerlingguy any intentions to merge this? |
|
No matter what, this would need rebasing as the project now uses GitHub Actions for CI. |
Can I help performing the rebase? In case @kgizdov does not react, I could replicate the patch and submit a PR myself. |
|
I will rebase on Mon ;) |
kgizdov
force-pushed
the
chicken_or_egg_user_db
branch
from
a187a87
to
007bd04
Compare
|
@geerlingguy rebased |
kgizdov
force-pushed
the
chicken_or_egg_user_db
branch
from
007bd04
to
8b3a63d
Compare
…igure the existing users Signed-off-by: Konstantin Gizdov <kgizdov@gmail.com>
kgizdov
force-pushed
the
chicken_or_egg_user_db
branch
from
8b3a63d
to
5223a02
Compare
As the title says. Attempts to fix #125