-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
terminus sites create
API call crashes with a Python backtrace
#1102
Comments
Obviously, if you pass the org's UUID in the |
It looks like there's an issue when looking up your organization's ID. I can't duplicate this error exactly - I can make it err without telling me my organization name is bad, but it won't give me a Python stacktrace. Would it be possible to get the |
I emailed you the debug output, but now the error is happening during a GET to I do know that I have had trouble yesterday and today with validating workflow-related tasks. In some cases Terminus was trapped in a perpetual loop of GETs on I did happen to capture a trace URL from yesterday's POST error: No idea if this will help. |
As of Today 0.13.1 is failing on site creates by not providing the site_name:
If I get enough free time this weekend I'll see if I can fix. |
terminus sites create --org=my-org --site=provisioning-test \ --label="Provisioning Test" --upstream=21e1fada-199c-492b-97bd-0b36b53a9da0
results in the an error. Upon further investigation, the following backtrace is given in the HTTP response:
It turns out that the following JSON payload is being sent:
The call succeeds if the
organization_id
is sent as a UUID instead of the org name.The text was updated successfully, but these errors were encountered: