In components/clp-py-utils/clp_py_utils/clp_config.py around lines 595-603, the
Presto host and port fields have no class-level defaults so callers must always
set them; add sensible defaults by giving host a default of
PRESTO_COORDINATOR_COMPONENT_NAME and port a default of DEFAULT_PORT (use
Pydantic Field or direct default assignment consistent with the model in this
file) so that instances created for the packaged setup get correct values while
still allowing overrides; leave transform_for_container() as-is to explicitly
set these values when transforming for container runtime.

In tools/deployment/presto-clp/scripts/init.py around lines 10 to 13, the
DATABASE_COMPONENT_NAME and DATABASE_DEFAULT_PORT are duplicated values that
should be imported from clp_py_utils.clp_config to avoid drift; replace the
hardcoded constants with imports from clp_py_utils.clp_config (import the two
names and use them directly), and if clp_py_utils is not available in this
runtime, add a short comment explaining why duplication is necessary and
implement a runtime check that compares the local constants to the values from
clp_py_utils (raising a clear error or logging and exiting if they differ).

Learnt from: junhaoliao
PR: y-scope/clp#1501
File: tools/deployment/presto-clp/scripts/init.py:10-13
Timestamp: 2025-10-27T07:07:37.889Z
Learning: In `tools/deployment/presto-clp/scripts/init.py`, the `DATABASE_COMPONENT_NAME` and `DATABASE_DEFAULT_PORT` constants are intentionally duplicated from `clp_py_utils.clp_config` because `clp_py_utils` is not installed in the Presto init script's runtime environment. The two flows are separate and this duplication is documented. There are plans to merge these flows after a future release.

---

🏁 Script executed:

```shell
#!/bin/bash
# Find _get_clp_package_instance_id function implementation
echo "=== Finding _get_clp_package_instance_id function ==="
rg -n '_get_clp_package_instance_id' tools/deployment/presto-clp/scripts/init.py -A 15

echo -e "\n=== Searching for CLP package docker-compose in repository ==="
fd -t f 'docker-compose' | grep -v presto-clp

echo -e "\n=== Searching for network configuration in CLP or clp-package ==="
fd -t f 'docker-compose.ya?ml' | xargs rg -l 'networks:' 2>/dev/null

---

🏁 Script executed:

```shell
#!/bin/bash
# Get full _get_clp_package_instance_id function
echo "=== Full _get_clp_package_instance_id function ==="
rg -n '_get_clp_package_instance_id' tools/deployment/presto-clp/scripts/init.py -A 25

echo -e "\n=== CLP package docker-compose.yaml networks and project config ==="
cat tools/deployment/package/docker-compose.yaml | rg -B 5 -A 10 'networks:|^services:|name:'

echo -e "\n=== CLP package docker-compose.base.yaml networks ==="
cat tools/deployment/package/docker-compose.base.yaml | rg -B 2 -A 10 'networks:'

---

🏁 Script executed:

```shell
#!/bin/bash
# Check if CLP package docker-compose defines networks explicitly
echo "=== Checking for explicit networks definition in CLP package ==="
cat tools/deployment/package/docker-compose.yaml | head -50
cat tools/deployment/package/docker-compose.base.yaml | grep -A 15 "networks:"

# Check if project name is dynamically set or if there's instance-id usage
echo -e "\n=== Looking for instance-id usage in deployment scripts ==="
fd -t f 'docker-compose|\.sh' tools/deployment/package/ | xargs grep -l 'instance' 2>/dev/null || echo "No instance-id references found"

# Check how the network is actually used
echo -e "\n=== Network name format consistency check ==="
grep -r 'clp-package.*_default\|instance.*id' tools/deployment/ --include='*.yaml' --include='*.yml' --include='*.py' | grep -E 'network|project' | head -20

---

🏁 Script executed:

```shell
#!/bin/bash
# Search for where instance-id file is created and how it's used
echo "=== Where is instance-id file created/written? ==="
rg -n 'instance-id' tools/deployment/ -B 3 -A 3 --include='*.py' --include='*.sh'

echo -e "\n=== Check if CLP package has any external networks defined ==="
cat tools/deployment/package/docker-compose.base.yaml

echo -e "\n=== Check for explicit network creation/configuration in scripts ==="
rg -n 'networks:' tools/deployment/package/ --include='*.yaml' -A 5

In tools/deployment/presto-clp/scripts/init.py around lines 169 to 172, the
constructed Docker network name uses a hyphen before the instance ID which
yields clp-package-{instance_id}_default; change this to use an underscore so
the network matches Docker Compose convention by setting
CLP_PACKAGE_NETWORK_NAME to clp-package_{instance_id}_default instead of
clp-package-{instance_id}_default.

#!/bin/bash
# Check the network name format in controller.py around line 603
echo "=== Checking controller.py line 603 and surrounding context ==="
cat components/clp-package-utils/clp_package_utils/controller.py | sed -n '595,615p'

echo -e "\n=== Search for all occurrences of network name construction in controller.py ==="
rg -n 'clp-package.*instance.*default|instance.*clp-package.*default' components/clp-package-utils/clp_package_utils/controller.py -B 2 -A 2

#!/bin/bash
# Search for network name patterns more broadly
echo "=== Search for 'clp-package' in controller.py ==="
rg -n 'clp-package' components/clp-package-utils/clp_package_utils/controller.py -C 3

echo -e "\n=== Search for 'instance' combined with 'network' or 'default' ==="
rg -n 'instance.*network|network.*instance|instance.*default' components/clp-package-utils/clp_package_utils/controller.py -C 2

echo -e "\n=== Check total lines in controller.py ==="
wc -l components/clp-package-utils/clp_package_utils/controller.py