docs: update documentation for microservices docker-compose

- Replace AIO/GD.CN terminology with GoodData throughout
- Add detailed docker-compose setup instructions to CONTRIBUTING.md
- Update test overview and comments to reflect new architecture
- Fix license key instructions (use build/license file)

jira: DX-319
risk: low

Author: Jan Tychtl

.openapi-generator/README.md

@@ -15,9 +15,9 @@ if no such exists or updates existing client code.
 Use prepared `make` targets from repository root:
 - `make api-client`
 
-Predefined targets use `http://gooddata-cn-ce:3000` URL to fetch OpenAPI schema and connect generator container to
-the `gooddata-python-sdk_default` network. It is prepared to be executed against running `docker-compose.yaml`
-services.
+Predefined targets use `http://localhost:3000` URL to fetch OpenAPI schema. If you need to connect to the GoodData
+services running in docker-compose, you can use the `gooddata-python-sdk_default` network. The docker-compose.yaml
+in the repository root starts all required GoodData microservices for testing and development.
 
 When you need to point generator to different schema source, use `generate_client.sh` script directly.
 Below is the example for `gooddata-scan-client` and schema on URL `https://my-gd-cn`, execute it from

CONTRIBUTING.md

@@ -182,23 +182,104 @@ Tests triggered by `make` can be controlled via these environment variables:
   ```
 
 ### How to update vcrpy tests
-Some tests include HTTP call(s) to GD.CN instance. That tests are executed through
-[vcrpy](https://vcrpy.readthedocs.io/) so that GD.CN instance is needed either first time or when request is changed.
+Some tests include HTTP call(s) to GoodData instance. Those tests are executed through
+[vcrpy](https://vcrpy.readthedocs.io/) so that a GoodData instance is needed either the first time or when a request is changed.
 It has clear benefits:
-- ability to run the tests without GD.CN
+- ability to run the tests without a GoodData instance
 - request and response snapshot - it makes debugging of HTTP calls simple
 
-But there is one disadvantage. One needs GD.CN instance with the original setup to change tests.
-`docker-compose.yaml` in root of the repository is here to help. It starts:
-- GD.CN AIO in selected version
-- postgres with gooddata-fdw extension
-- service which setups GD.CN AIO demo project including PDM, LDM, metrics and visualizations
+But there is one disadvantage. One needs a GoodData instance with the original setup to change tests.
+`docker-compose.yaml` in the root of the repository is here to help.
+
+#### Prerequisites for Running Tests Locally
+
+1. **AWS ECR Login** - The docker-compose uses ECR images:
+   ```bash
+   aws ecr get-login-password | docker login --username AWS --password-stdin 020413372491.dkr.ecr.us-east-1.amazonaws.com
+   ```
+
+2. **GoodData License Key** - Get from the GoodData team and place it in the `./build/license` file:
+   ```bash
+   mkdir -p build
+   echo "<your_license_key>" > build/license
+   ```
+   The auth-service reads the license from this mounted location.
+
+#### What docker-compose starts
+
+The docker-compose starts a full GoodData microservices stack:
+
+**Infrastructure services:**
+- PostgreSQL (with demo databases: `md`, `dex`, `automation`, `gw`, `tiger`)
+- Redis (caching)
+- Apache Pulsar (messaging)
+- Traefik (routing)
+- Dex (OIDC authentication)
+
+**Core GoodData services:**
+- metadata-api, auth-service, calcique, sql-executor, result-cache
+- afm-exec-api, scan-model, api-gateway, api-gw
+- automation, export-controller, tabular-exporter
+- quiver (data processing engine)
+
+**Bootstrap services (run once):**
+- `metadata-organization-bootstrap` - Creates organization + admin user
+- `data-loader` - Loads demo data into PostgreSQL (with `--no-schema-versioning`)
+- `create-ds` - Registers data sources in metadata-api
+- `layout-uploader` - Uploads workspace hierarchy, analytics model, users, permissions
+
+#### The `--no-schema-versioning` Flag
+
+The data-loader uses `--no-schema-versioning` flag to ensure:
+- Schema names are consistent (e.g., `demo` not `demo_abc123`)
+- Fixture names don't have hash suffixes
+- VCR cassette tests produce reproducible results
+
+#### Starting GoodData for Tests
+
+```bash
+# Start all services
+docker compose up -d
+
+# Wait for bootstrap to complete (watch for "Layout upload completed successfully!")
+docker compose logs -f metadata-organization-bootstrap data-loader create-ds layout-uploader
+
+# Check service status
+docker compose ps
+
+# The GoodData API is available at http://localhost:3000
+# Default credentials: demo@example.com / demo123
+# API token: YWRtaW46Ym9vdHN0cmFwOmFkbWluMTIz
+```
+
+#### Updating vcrpy Cassettes
 
 When a vcrpy supported test needs to be updated:
-- start GD.CN using above `docker-compose.yaml`
-- delete original vcrpy cassette with `make remove-cassettes`
-- execute test
-- update a newly generated cassette to the git
+- Start GoodData using the above `docker-compose.yaml`
+- Wait for all bootstrap services to complete
+- Delete original vcrpy cassette with `make remove-cassettes`
+- Execute test
+- Commit the newly generated cassette to git
+
+#### Stopping and Cleanup
+
+```bash
+# Stop all services
+docker compose down
+
+# Full cleanup (remove volumes - required for fresh start)
+docker compose down -v
+```
+
+#### Running gooddata-fdw Tests
+
+The FDW (Foreign Data Wrapper) tests require an additional service. Start it with:
+
+```bash
+docker compose --profile fdw up -d
+```
+
+This starts a PostgreSQL instance with the gooddata-fdw extension on port 2543.
 
 ## Run continuous integration tests
 Tests in pull request (PR) are executed using docker. The following is done to make test environment as close
@@ -229,7 +310,7 @@ venv automatically. So when docker tox tests are executed after localhost tests
   ```bash
   TEST_ENVS=py311,py310 ADD_ARGS="-k http_headers" make test-ci
   ```
-- run tests on localhost against all-in-one image started with docker-compose
+- run tests on localhost against microservices started with docker-compose
   ```bash
   RECREATE_ENVS=1 HOST_NETWORK=1 make test-ci
   ```

clients_README.md

@@ -1,6 +1,6 @@
 # Generated API Clients
 
-The generated client provide Python classes that you can use to call GoodData.CN REST APIs. The client contains
+The generated client provides Python classes that you can use to call GoodData REST APIs. The client contains
 models for API requests and responses and controllers to actually call the APIs.
 
 We recommend using the gooddata_sdk package where possible because:

docker-compose.yaml

@@ -11,7 +11,7 @@
 #    aws ecr get-login-password | docker login --username AWS --password-stdin 020413372491.dkr.ecr.us-east-1.amazonaws.com
 #
 # 2. GoodData license key (get from GoodData team):
-#    export GDCN_LICENSE_KEY=<your_license_key>
+#    mkdir -p build && echo "<your_license_key>" > build/license
 #
 # ============================================================================
 # WORKFLOW
@@ -43,10 +43,10 @@
 # USAGE
 # ============================================================================
 #   # Start all services:
-#   GDCN_LICENSE_KEY=<key> docker compose up -d
+#   docker compose up -d
 #
 #   # Wait for bootstrap to complete:
-#   docker compose logs -f metadata-organization-bootstrap data-loader create-ds
+#   docker compose logs -f metadata-organization-bootstrap data-loader create-ds layout-uploader
 #
 #   # Check service status:
 #   docker compose ps

packages/gooddata-dbt/src/gooddata_dbt/dbt_plugin.py

@@ -21,7 +21,7 @@
 from gooddata_dbt.sdk_wrapper import GoodDataSdkWrapper
 from gooddata_dbt.utils import get_duration, report_message_to_git_vendor
 
-# TODO - upgrade AIO, cleanup, start from scratch, test everything
+# TODO - cleanup, start from scratch, test everything
 
 GOODDATA_LAYOUTS_DIR = Path("gooddata_layouts")
 

packages/gooddata-dbt/src/gooddata_dbt/sdk_wrapper.py

@@ -9,7 +9,7 @@
 
 
 class GoodDataSdkWrapper:
-    # Timeout=600 because supporting waiting for All-in-one image starts
+    # Timeout=600 because supporting waiting for GoodData services to start
     def __init__(
         self, args: argparse.Namespace, logger: Logger, profile: Optional[str] = None, timeout: int = 600
     ) -> None:

packages/gooddata-pandas/tests/dataframe/test_dataframe_for_insight.py

@@ -13,7 +13,7 @@
 @gd_vcr.use_cassette(str(_fixtures_dir / "dataframe_for_visualization_date.yaml"))
 def test_dataframe_for_visualization_date(gdf: DataFrameFactory):
     # 2 metrics grouped by date dimension with data for last 12 months
-    # exact numbers cannot be checked as date data are changed each AIO build
+    # exact numbers cannot be checked as date data are changed each build
     df = gdf.for_visualization(visualization_id="customers_trend")
 
     assert len(df) == 12

packages/gooddata-sdk/tests/catalog/test_catalog_data_source.py

@@ -652,7 +652,7 @@ def test_scan_model(test_config):
     with pytest.raises(ValueError):
         CatalogScanModelRequest(scan_tables=False, scan_views=False)
 
-    # TODO - how to simulate warnings in AIO?
+    # TODO - how to simulate warnings in the test environment?
     assert len(scan_result.warnings) == 0
 
 

packages/gooddata-sdk/tests/compute/test_compute_service.py

@@ -8,7 +8,7 @@
 
 # Skip all tests in this module
 pytest.skip(
-    "Skipping all tests in this module because it requires gen-ai which is not available in AIO.",
+    "Skipping all tests in this module because it requires gen-ai which is not available in the test environment.",
     allow_module_level=True,
 )
 

packages/gooddata-sdk/tests/overview.md

@@ -38,9 +38,12 @@ will find that the data in snapshots does not match the conventions of the API.
 
 ## Component tests with vcrpy
 
-The vcrpy simplifies mocking HTTP endpoints. The component tests use the AIO image environment and the demo
-workspace. The connection details are stored in [gd_test_config.yaml](gd_test_config.yaml). Tests accept command
-line parameter `--gd-test-config` to pass custom test configuration.
+The vcrpy simplifies mocking HTTP endpoints. The component tests use the GoodData microservices environment
+(started via `docker-compose.yaml` in the repository root) and the demo workspace. The connection details are
+stored in [gd_test_config.yaml](gd_test_config.yaml). Tests accept command line parameter `--gd-test-config`
+to pass custom test configuration.
+
+See [CONTRIBUTING.md](../../../CONTRIBUTING.md) for detailed instructions on setting up the test environment.
 
 Additionally, make sure that every time you use vcrpy, you configure the tool:
 - to not store the 'Authorization' token and 'user-agent' in the captured data