microsoft / microsoft/AzureTRE
Make an existing resource template the current version
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
Describe the bug
Cannot make existing resource template the "current" version, or delete the one incorrectly registered as false.
Steps to reproduce
- Register a template with current=false
- Now blocked unless edit the bundle and add a new version.
Template registration experience needs some more thought. We should discuss this "journey" prior to trying to fix. Would like to decouple publishing vs registration, and make the registration process just a case of providing registry/image details.
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
No files, tests, or entry points are named. Start by tracing the resource-template registration flow and reviewing the proposed publishing-versus-registration journey with maintainers; done requires an agreed design that allows an existing template to become current and handles incorrectly registered versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100