ATE: describe `eval_schema_update.yml` playbook
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Product: ATE
Root document: https://www.tarantool.io/ru/devops/latest/docker-scenarios-common/ (?)
Since: ???
SME: @ Satbek @ opomuc @ lastoCHka42
Details
В доке ATE нужно описать плейбук eval_schema_update.yml для обновления схемы в кластере (box.schema.upgrade).
См мр: https://gitlab.corp.mail.ru/tarantool/tdb/tarantooldb/-/merge_requests/173/diffs
См также: https://www.tarantool.io/en/doc/latest/reference/reference_lua/box_schema/upgrade/
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ATE root document at the linked Tarantool documentation page and review the eval_schema_update.yml playbook mentioned in the issue. Use the linked merge request and box.schema.upgrade reference to establish the documented behavior; done means the ATE documentation explains how the playbook updates the cluster schema.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100