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.

Sign up for GitHub

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

Jump to bottom

As a developer, I want a record of significant changes to our deploy process so that I can refer to it when creating and updating playbooks. #50

Closed
thatbudakguy opened this issue Dec 14, 2020 · 0 comments · Fixed by #51
Closed

As a developer, I want a record of significant changes to our deploy process so that I can refer to it when creating and updating playbooks. #50

thatbudakguy opened this issue Dec 14, 2020 · 0 comments · Fixed by #51
Labels
📖 documentation Improvements or additions to documentation

Comments

@thatbudakguy
Copy link
Contributor

We need a system to document major decisions/changes to the way we use ansible. One option is to use the ADR (architectural decision record) spec, like PUL does in princeton-ansible.

Discussion:

Would you add a note about dropping these in a changelog? (Or do we even have a changelog? Maybe we don't, because no releases...) Would it make sense to start?

Originally posted by @rlskoeser in #49 (comment)
@thatbudakguy thatbudakguy changed the title Document architectural decisions As a developer, I want a record of significant changes to our deploy process so that I can refer to it when creating and updating playbooks. Dec 14, 2020
@thatbudakguy thatbudakguy linked a pull request Dec 14, 2020 that will close this issue
Document architectural decisions #51
Merged
@thatbudakguy thatbudakguy added the 📖 documentation Improvements or additions to documentation label Dec 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
📖 documentation Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Document architectural decisions Princeton-CDH/cdh-ansible
1 participant
@thatbudakguy