Cp-ansible: Connectors are unarchived and do not necessarily have the correct permissions
Deploying a new connector via archive does not necessarily set the correct permission automatically.
When you have a strong umask for your ansibe user, you might run into issues.
suggested solution:
Add concret permissions in the unarchive task.
Fobhep
All 6 comments
Is this what you are looking for: https://github.com/confluentinc/cp-ansible/pull/368
domenicbove
on 16 Jul 2020
Wow I just saw your PR lol!
I actually assumed you knew the fix to this as I was doing it @Fobhep
domenicbove
on 16 Jul 2020
@domenicbove oha sorry :D
You opened your PR after mine, right? Or did I open one without seeing that you already had one open?
Should I for future PRs add a line in the issue that I intend to fix this immediately?
Fobhep
on 16 Jul 2020
Mine was second, don't change your process!
domenicbove
on 16 Jul 2020
@Fobhep this can be closed right? I merged your pr up thru 5.5.1 and higher branches
domenicbove
on 17 Jul 2020
@domenicbove yup!
Fobhep
on 17 Jul 2020
Related issues
LGouellec
·
4Comments
chuck-confluent
·
5Comments
Fobhep
·
7Comments
sandeeprapido
·
9Comments
Fobhep
·
12Comments
Most helpful comment
Is this what you are looking for: https://github.com/confluentinc/cp-ansible/pull/368