Arpad Müller 527cdbc010 Don't require AWS access keys for S3 pytests (#6556) ...

Don't require AWS access keys (AWS_ACCESS_KEY_ID and
AWS_SECRET_ACCESS_KEY) for S3 usage in the pytests, and also allow
AWS_PROFILE to be passed.

One of the two methods is required however.

This allows local development like:

```
aws sso login --profile dev
export ENABLE_REAL_S3_REMOTE_STORAGE=nonempty REMOTE_STORAGE_S3_REGION=eu-central-1 REMOTE_STORAGE_S3_BUCKET=neon-github-ci-tests AWS_PROFILE=dev
cargo build_testing && RUST_BACKTRACE=1 ./scripts/pytest -k debug-pg16 test_runner/regress/test_tenant_delete.py::test_tenant_delete_smoke
```

related earlier PR for the cargo unit tests of the `remote_storage` crate: #6202

---------

Co-authored-by: Alexander Bayandin <alexander@neon.tech>

2024-02-01 20:18:07 +00:00

..

attachment_service

control_plane/attachment_service: make --path optional (#6545)

2024-01-31 17:02:41 +00:00

src

Don't require AWS access keys for S3 pytests (#6556)

2024-02-01 20:18:07 +00:00

.gitignore

Revert "Use actual temporary dir for pageserver unit tests"

2023-01-19 20:16:56 +01:00

Cargo.toml

control_plane: database persistence for attachment_service (#6468)

2024-01-26 17:20:44 +00:00

safekeepers.conf

Separate mgmt and libpq authentication configs in pageserver. (#3773)

2023-03-15 13:52:29 +02:00

simple.conf

tests: enable multiple pageservers in neon_local and neon_fixture (#5231)

2023-09-08 16:19:57 +01:00