Skip to content
This repository has been archived by the owner on Jan 12, 2023. It is now read-only.

Use varibales for playbook #44

Open
cworf91 opened this issue Apr 9, 2021 · 0 comments
Open

Use varibales for playbook #44

cworf91 opened this issue Apr 9, 2021 · 0 comments
Assignees
Labels
Milestone

Comments

@cworf91
Copy link
Member

cworf91 commented Apr 9, 2021

Summary

The playbook should be as generic as posible. Therefore, it is necessary to use variables. The variables should be provide in a different file (var.yml), so that the user can customize the playbook in a efficient way.

Acceptance criteria

[ ] playbook without hardcoded values
[ ] var.yml with varibales
[ ] playbook is still working

@GoebelL GoebelL added the P4 label Apr 26, 2021
@GoebelL GoebelL added this to the 19.2 Sprint 7 milestone May 31, 2021
@GoebelL GoebelL modified the milestones: 19.2 Sprint 7, 19.2 Sprint 8 Jun 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants