overlays: file-add should allow replacing existing files (or add a file-replace)
Maintainers usually reply within 7 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by locating the overlay command implementation and any tests for file-add and file-remove. Compare the existing failure behavior with the requested replacement workflow, then establish whether file-add should replace files or a separate file-replace command is needed; done means the chosen behavior is implemented and covered by tests.
Written by the indexing model from the issue text.
Description
A common use case for file-add will be to replace an existing file with one of our own containing different content, so it doesn't make sense to require users to do file-remove then immediately file-add with the same file. if we want to leave file-add failing if the file exists, then there should be a file-replace command added that works like file-add but allows replacing an existing file.
--
Imported on behalf of @ddstreet
- Dominant language
- Go
- Stars
- 18
- Forks
- 29
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 19
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from microsoft/azure-linux-dev-tools
-
`patch-add` overlay appends `PatchN:` tag at end of preamble instead of grouping with existing Patch tagsPossibly taken @IzanVil claimed this 13 days ago. Openarea: overlays enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/azure-linux-dev-tools#284 · 2 comments ·
Maintainers usually reply within 7 days
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
microsoft/azure-linux-dev-tools#374 ·
Maintainers usually reply within 7 days
-
[Bug]: no specification for TOML object modelMay be free again @ddstreet claimed this 39 days ago, and no pull request is open. Openbug
microsoft/azure-linux-dev-tools#318 · 1 comment · 1 assignee ·
Maintainers usually reply within 7 days
-
[Bug]: azldev comp render doesn't always add changelog entriesMay be free again @ddstreet claimed this 51 days ago, and no pull request is open. Openbug GA blocker
microsoft/azure-linux-dev-tools#316 · 1 assignee ·
Maintainers usually reply within 7 days
-
config dump omits per-file overlays and inherited default-component-configPossibly taken @liunan-ms claimed this 51 days ago. Openbug GA blocker
microsoft/azure-linux-dev-tools#264 · 1 assignee ·
Maintainers usually reply within 7 days
All issues in microsoft/azure-linux-dev-tools
Similar issues
-
bug frontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
oalders/clodhopper#133 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
peasant-labs/peasant#596 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hatchet-dev/hatchet#5179 ·
Maintainers usually reply within 1 day
-
bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
FairwindsOps/nova#484 ·