-
Notifications
You must be signed in to change notification settings - Fork 147
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
How to debug a 409 from the TRE CLI? #4080
Comments
Hey @TonyWildish-BH a 409 error for that command is version exists
Agreed logging could be better. Also doesnt look like you have enough fields in your json file |
hi @tim-allen-ck. I'm not trying to register a shared service, I'm trying to deploy one from an existing template. Can you tell me what fields are missing? I'm trawling the code to find out what should be in there. |
My mistake. This line then: AzureTRE/api_app/api/routes/shared_services.py Lines 62 to 63 in 9c59b80
template_schema.json
{
"$schema": "http://json-schema.org/draft-07/schema",
"$id": "./templates/shared_services/service_name/template_schema.json",
"type": "object",
"title": "New Shared Service",
"description": "A shared service",
"properties": {},
"required": []
} |
For the
and I have both those, so that should be OK. Any idea what else could be causing my 409? |
No, I'm deploying into an empty TRE, there's no other CERT service anywhere. |
Definitely nothing in the Cosmos DB? You will have to look at the API logs to get more details https://microsoft.github.io/AzureTRE/v0.19.0/troubleshooting-faq/app-insights-logs/ |
this was with a virgin TRE, I deployed from scratch (with a new TRE_ID) explicitly to have a clean environment. |
Can you see anything in the logs? |
no, nothing in the logs... |
I'm trying to automate creating some shared services etc with the CLI, and getting a 409 return code with no error message. How can I debug this and find out what the problem is?
Steps to reproduce
My specific example is a certificate service for Nexus. I have a JSON file, as follows:
I run the CLI:
tre shared-services new --definition-file my-definition.json
and I get this response:
what can I do to debug this?
This is using the latest version of the CLI, installed just a few minutes ago.
N.B. Other commands work fine, creating workspaces etc, so my basic installation is good and I'm logged in to the TRE.
The text was updated successfully, but these errors were encountered: