Should we put the published module in the module cache?
Open
enhancement
good first issue
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
Some users insist on overwriting an existing tag when publishing their modules to the registry. If they want to immediately validate or consume the module they will have to either run force restore or delete the existing module from the cache.
Should we do it for them automatically?
Contributor guide
Research direction
No files, tests, or entry points are identified. Review the module publishing and cache behavior first, then determine whether automatically updating the cache after overwriting a registry tag is desired and how completion would be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100