microsoft / microsoft/AzureTRE
How to debug a 409 from the TRE CLI?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
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:
{
"templateName": "tre-shared-service-certs",
"properties": {
"display_name": "nexus-ssl certificate service",
"description": "automated deployment",
"cert_name": "nexus-ssl",
"domain_prefix": "nexus"
}
}
I run the CLI:
tre shared-services new --definition-file my-definition.json
and I get this response:
Creating shared_service...
{
"status_code": 409,
"body": ""
}
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the empty 409 with tre shared-services new --definition-file my-definition.json and the supplied certificate-service definition. Trace how the CLI handles the shared-service creation response; done means the failure exposes an actionable error or a clear way to debug the cause.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100