aplbrain / saber

Apache License 2.0
14 stars 2 forks source link

Conduit build should raise warning when ECR repository cannot be created? #9

Open erikjohnson24 opened 5 years ago

erikjohnson24 commented 5 years ago

Currently this is the output when conduit build fails to create an ECR repository. Perhaps this should raise a helpful warning instead?

[2019-06-24 23:26:36,392] {job_definitions.py:264} INFO - Successfully tagged ecrrepo/aplbrain/gtunets_gpu:s3

[2019-06-24 23:26:36,398] {job_definitions.py:270} INFO - The push refers to repository [ecrrepo/aplbrain/gtunets_gpu] [2019-06-24 23:26:36,407] {job_definitions.py:270} INFO - Preparing [2019-06-24 23:26:36,408] {job_definitions.py:270} INFO - Waiting [2019-06-24 23:26:36,409] {job_definitions.py:270} INFO - Preparing [2019-06-24 23:26:36,409] {job_definitions.py:270} INFO - Waiting [2019-06-24 23:26:36,409] {job_definitions.py:270} INFO - Preparing [2019-06-24 23:26:36,409] {job_definitions.py:270} INFO - Waiting [2019-06-24 23:26:36,409] {job_definitions.py:270} INFO - Preparing [2019-06-24 23:26:36,410] {job_definitions.py:270} INFO - Waiting [2019-06-24 23:26:36,410] {job_definitions.py:270} INFO - Preparing [2019-06-24 23:26:36,410] {job_definitions.py:270} INFO - Waiting [2019-06-24 23:26:36,411] {job_definitions.py:270} INFO - Preparing [2019-06-24 23:26:36,411] {job_definitions.py:270} INFO - Waiting [2019-06-24 23:26:36,411] {job_definitions.py:270} INFO - Preparing [2019-06-24 23:26:36,412] {job_definitions.py:270} INFO - Waiting [2019-06-24 23:26:36,412] {job_definitions.py:270} INFO - Preparing [2019-06-24 23:26:36,412] {job_definitions.py:270} INFO - Waiting [2019-06-24 23:26:36,412] {job_definitions.py:270} INFO - Preparing [2019-06-24 23:26:36,412] {job_definitions.py:270} INFO - Waiting [2019-06-24 23:26:36,412] {job_definitions.py:270} INFO - Preparing [2019-06-24 23:26:36,413] {job_definitions.py:270} INFO - Waiting

dxenes1 commented 5 years ago

any idea on how I can replicate this?

erikjohnson24 commented 5 years ago

I think this would require a user whose IAM permissions do not include ECR