Summary
Since our playbooks should be executed on the same VM, it must be possible to edit the playbooks on this VM and push them in git.
Details
Git has a global configuration file. The user oscm-automaton is stored this config with his email adress. If a current status is pushed to github, the user oscm-automaton is shown in the history. However, a change should be able to be assigned to the respective user. Therefore, with this task, a possibility should be found to push under his own name (own github account) without changing the global configuration.
Acceptance criteria
[ ] oscm-automaton is still in the global setting
[ ] local configuration allows to push with own user
Summary Since our playbooks should be executed on the same VM, it must be possible to edit the playbooks on this VM and push them in git.
Details Git has a global configuration file. The user oscm-automaton is stored this config with his email adress. If a current status is pushed to github, the user oscm-automaton is shown in the history. However, a change should be able to be assigned to the respective user. Therefore, with this task, a possibility should be found to push under his own name (own github account) without changing the global configuration.
Acceptance criteria [ ] oscm-automaton is still in the global setting [ ] local configuration allows to push with own user