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

enable sourcing environment file within wrapper #536

Merged
merged 2 commits into from
Mar 24, 2023
Merged

enable sourcing environment file within wrapper #536

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f73c74a
enable sourcing environment file within wrapper
rtib Oct 17, 2022
297bedb
docs
rtib Feb 23, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
3 changes: 3 additions & 0 deletions bin/medusa-wrapper
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,9 @@ if test -f pid; then
done
exit $(cat status)
fi
if [ -f /etc/default/cassandra-medusa ]; then
. /etc/default/cassandra-medusa
fi
$@ >stdout 2>stderr &
echo $! >pid
wait $!
Expand Down
6 changes: 6 additions & 0 deletions docs/Configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -169,3 +169,9 @@ Some config settings can be overriden through environment variables prefixed wit
| `sstableloader_tspw` | `MEDUSA_SSTABLELOADER_TSPW` |
| `sstableloader_kspw` | `MEDUSA_SSTABLELOADER_KSPW` |
| `resolve_ip_addresses` | `MEDUSA_RESOLVE_IP_ADDRESSES` |

### Sourcing environment variables

If you are using environment variables to override some settings, you can source a file containing the environment variables before running Medusa commands. For example, if you have a file named `/etc/default/cassandra-medusa` containing exported environment variables.

These variables will also be available when running Medusa cluster commands, e.g. backup-cluster.
8 changes: 7 additions & 1 deletion docs/minio_setup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,4 +29,10 @@ secure = False
```

Medusa should now be able to access the bucket and perform all required operations.
*Note: MinIO and other self hosted S3 compatible storage systems can only be used in unsecured (non SSL) mode with Medusa due to limitations in Apache Libcloud. Cloud hosted S3 compatible backends (such as IBM) should be able/require to use secured access.*
*Note: By default, MinIO and other self hosted S3 compatible storage systems can only be used in unsecured (non SSL) mode with Medusa due to limitations in Apache Libcloud. To enable SSL access to self hosted S3 compatible storage systems, you will need to set the environment variable `SSL_CERT_FILE` to the path of a valid certificate file containing trusted CA certificates of your S3 service. In order to get cluster wide commands working properly, you will need to set this in the `/etc/default/cassandra-medusa` file on all nodes running Medusa containing:*

```bash
export SSL_CERT_FILE=/path/to/certfile
```

*Cloud hosted S3 compatible backends (such as IBM) should be able/require to use secured access.*