When doing draft --environment=some-env up --auto-connect, auto-connect connects to the instance in the default environment, not the one in some-env
Also, the command above specifies a message similar to the following:
Inspect the logs with 'draft logs 01CSC7N10KQ1MZVMYHRQJQXBSV'
This is wrong as well because draft logs will search for the hash in the default environment, and it will report an error similar to the following Error: could not read logs for 01CSC7N10KQ1MZVMYHRQJQXBSV: open ~path-to-default-env-logs~/01CSC7N10KQ1MZVMYHRQJQXBSV: no such file or directory
The correct command would be: draft logs --environment=some-env 01CSC7N10KQ1MZVMYHRQJQXBSV
When doing
draft --environment=some-env up --auto-connect, auto-connect connects to the instance in the default environment, not the one insome-envAlso, the command above specifies a message similar to the following:
Inspect the logs with 'draft logs 01CSC7N10KQ1MZVMYHRQJQXBSV'This is wrong as well because
draft logswill search for the hash in the default environment, and it will report an error similar to the followingError: could not read logs for 01CSC7N10KQ1MZVMYHRQJQXBSV: open ~path-to-default-env-logs~/01CSC7N10KQ1MZVMYHRQJQXBSV: no such file or directoryThe correct command would be:
draft logs --environment=some-env 01CSC7N10KQ1MZVMYHRQJQXBSV