Running cli command db import with STDIN doesn't work

[roborourke]

Running cli command db import with STDIN doesn't work

[roborourke]

Note, removing pseudo-terminal allocation (-t) from the docker exec call in this instance fixes the problem.

@joehoyle @rmccue I'm not super familiar with this aspect of WP CLI, the isPiped detection and TTY allocation. Is < an edge case that we need to handle specially or is the logic in the PHP at fault?

[svandragt]

As @roborourke mentioned:

if the db dump is in the working directory then it’s available on the container and you can do composer server cli -- db import database.sql

If the import is successful you should see more than one post when running composer server cli -- post list --limit=10

[roborourke]

Related to #224

[rmccue]

If we can't get this closed out this sprint, let's reassess as it's been in here for a while.

[roborourke]

We actually updated the docs to explicitly say it needs to be within the project root, so the problem with the documented solution is fixed at least.

[rmccue]

So, no more bug? We can close?

[roborourke]

We can say it's not a supported use-case I guess, nothing else along these lines has really come up since. I'll close so we don't waste more time on it until there's more reasons to dig into TTY / piping-of-things support and use-cases.