You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some context: initially we have an app created via cartridge-cli, later migration to tt was carried out. tt init was called inside the app folder, with instances_enabled: "." in tt.yaml. Everything is fine, but instance naming is wierd, instance name contains dot instead of app name.
repro:
mkdir repro
cd repro
tt init
tt create cartridge --name app
cd app
tt init
tt --cfg tt.yaml status
actual output:
.:s1-replica NOT RUNNING
.:s2-master NOT RUNNING
.:s2-replica NOT RUNNING
.:stateboard NOT RUNNING
.:router NOT RUNNING
.:s1-master NOT RUNNING
expected output:
app:s2-replica NOT RUNNING
app:stateboard NOT RUNNING
app:router NOT RUNNING
app:s1-master NOT RUNNING
app:s1-replica NOT RUNNING
app:s2-master NOT RUNNING
The text was updated successfully, but these errors were encountered:
@psergee is it duplicate of #843 or another problem?
It looks like other issue. tt must take base dir base as an app name.
Anyway, don't understand the purpose of the tt init + tt create + tt init set of commands.
Some context: initially we have an app created via cartridge-cli, later migration to tt was carried out.
tt init
was called inside the app folder, withinstances_enabled: "."
in tt.yaml. Everything is fine, but instance naming is wierd, instance name contains dot instead of app name.repro:
actual output:
expected output:
The text was updated successfully, but these errors were encountered: