Removing the wait limit on project_info when exiting a successful project creation. We already have confirmation from the action queue that the project creation was successful, so there is reason for optimism that we are just waiting for the API to receive the update itself.
Load testing demonstrates this is working well; e.g.
for i in 0 1 2 3 4 5 6 7 8 9; do for j in 0 1 2 3 4 5 6 7 8 9; do (ae5 project upload ~/Downloads/Hello-Anaconda-Enterprise.tar.bz2 --name test$i$ &)j; done; done
However, if you really don't want to wait the half-second required to see this, you can pass the --no-wait flag to project upload or sample clone commands. However, if you take this route, you will not receive an info record from the call.
Removing the wait limit on
project_infowhen exiting a successful project creation. We already have confirmation from the action queue that the project creation was successful, so there is reason for optimism that we are just waiting for the API to receive the update itself.Load testing demonstrates this is working well; e.g.
However, if you really don't want to wait the half-second required to see this, you can pass the
--no-waitflag to project upload or sample clone commands. However, if you take this route, you will not receive an info record from the call.