You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know this can become massive and maybe a little harder to manage since it can be over 30 roles but, git project management wise it might be better that each role has its own git repository. This can be helpful because anyone can git clone the role they want, better integration with ansible galaxy and easier CI/CD with molecule using different tools.
The text was updated successfully, but these errors were encountered:
I agree with @jlozadad - almost all other software development projects (Java, Python, Ruby, NodeJS, etc.) separate dependencies into their own software repository. By doing so, it ensures that the dependency is developed without too much influence by where it is being integrated. The interfaces are better designed, and testing/CI processes are more targeted and simpler. This same sort of philosophy should apply with roles as well.
I know this can become massive and maybe a little harder to manage since it can be over 30 roles but, git project management wise it might be better that each role has its own git repository. This can be helpful because anyone can git clone the role they want, better integration with ansible galaxy and easier CI/CD with molecule using different tools.
The text was updated successfully, but these errors were encountered: