[Doc] Inconsistencies in bookie instance type and terraform related command
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 160
Description
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
### What issue do you find in Pulsar docs?
The docs needs updation on the below
a) The documentation says, the bookie is of i3.xlarge, but the instances.tf says it is i3.4xlarge
b) To get the pulsar service url, the instruction to cat from terraform.state needs to be corrected. It should be `cat terraform.tfstate | jq .outputs.pulsar_service_url.value` instead of `cat terraform.tfstate | jq . modules[0].outputs.pulsar_service_url.value`
### What is your suggestion?
The docs needs updation on the below
a) The documentation says, the bookie is of i3.xlarge, but the instances.tf says it is i3.4xlarge
b) To get the pulsar service url, the instruction to cat from terraform.state needs to be corrected. It should be `cat terraform.tfstate | jq .outputs.pulsar_service_url.value` instead of `cat terraform.tfstate | jq . modules[0].outputs.pulsar_service_url.value`
### Any reference?
_No response_
### Are you willing to submit a PR?
- [X] I'm willing to submit a PR!
Contributor guide
Research direction
Locate the documentation describing the bookie instance type and the Terraform service-URL command, then compare them with instances.tf and the terraform.tfstate output structure. Update the instance size and jq command to match the reported values, and verify both corrected snippets in the rendered documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- terraform
- Domain
- documentation, infrastructure
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100