dave2wave commented on issue #9084:
URL: https://github.com/apache/pulsar/issues/9084#issuecomment-1049306564
If you are not in `us-east-1` then you can workaround this issue in
`broker.conf`
I'm using terraform and ansible - here's the `broker.conf` template
```
s3ManagedLedgerOffloadBucket={{ s3_bucket }}
s3ManagedLedgerOffloadRegion={{ s3_region }}
s3ManagedLedgerOffloadServiceEndpoint={{ s3_url }}
```
Here is the setting of these facts in the ansible playbook.
```
s3_bucket: "{{ tf_s3_bucket }}"
s3_region: "{{ tf_s3_region }}"
s3_url: "https://{{ tf_s3_bucket }}.s3.{{ tf_s3_region
}}.amazonaws.com"
```
I read the bucket and region from a file created by terraform:
```
- name: Get variables from terraform
include_vars: ./tf_ansible_vars.yaml
```
In terraform the bucket and region are from the `terraform.tfvars` and
written like so:
```
region = "us-west-2"
ami = "ami-9fa343e7" // RHEL-7.4
s3_bucket = "omb-testing-1"
```
```
# Export Terraform variable values to an Ansible var_file
resource "local_file" "tf_ansible_vars" {
content = <<-DOC
tf_s3_bucket: ${var.s3_bucket}
tf_s3_region: ${var.region}
DOC
filename = "./tf_ansible_vars.yaml"
}
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
