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

Consider applying mode permissions to vim/tmux/bash/etc clones and links #13

Open
marcus-grant opened this issue Oct 25, 2021 · 0 comments
Labels
low-priority Low priority items, nice to haves.

Comments

@marcus-grant
Copy link
Owner

There's an idempotency and functionality problem with roles that try to force pull downstream changes to dotfiles to remote machines. Because explicitly setting a mode to the cloned repo & the links pointing to them changes the permissisions modes of those entities, the git module getects changes and keeps trying to force pull the remote repo with different permissions. This means that every time the role is run with vim_git_force enabled and the remote repo has different permissions it will force pull those changes and there's no idempotency even though nothing else changed locally. This means that a few solutions are possible:

  • Add the skip_ansible_lint tag to these steps so the linter doesn't complain about a lack of permissions and forget worrying about them for this role
    • This feels hacky, but also, for most my dotfiles the permissions should just be whatever the dotfiles repo has them
@marcus-grant marcus-grant added the low-priority Low priority items, nice to haves. label Oct 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low-priority Low priority items, nice to haves.
Projects
None yet
Development

No branches or pull requests

1 participant