ATE: describe `check_3_0.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: @ opomuc @ lastoCHka42
Details
В доке ATE нужно описать плейбук check_3_0.yml для проверки работоспособности,сейчас описан такой плейбук только для tarantool cartridge:
https://www.tarantool.io/ru/devops/latest/docker-scenarios-common/#ate-admin-check-is-healthy
Плейбук check_3_0.yml не описан, но упоминается тут: https://www.tarantool.io/en/devops/latest/docker-scenarios-products/#ate-basic-ee-update-3x
Андрей Солодухин (15.10.2025 09:24):
Сценарий
check_is_healthy.yml
работает для 3 тарантула?Анна Балаева (15.10.2025 10:10):
Да, прошу прощения, для 3 тарантула аналогичную задачу выполняет плейбук check_3_0
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 and the existing ate-admin-check-is-healthy section, then review the check_3_0.yml reference on the ATE Basic EE Update 3x page. Describe what the playbook checks and how it is used for Tarantool 3, with a link from the relevant documentation section. Done means the playbook is documented alongside the existing health-check guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100