Feature Request
Add .gitignore-style exclusion handling to azd code deploy via a user-customizable .azdignore file.
Background
Follow-up to the "Feature/code deploy zip upload" PR. From the review discussion:
Good idea. Will add .azdignore file support as a follow-up PR. For now, added .azure/, .env, and .env.* to the hardcoded exclusion list to address the immediate security concern. The follow-up will let users customize exclusions.
Today, exclusions are hardcoded. Users need a way to customize what gets uploaded (e.g., node_modules/, build artifacts, local caches).
Proposed
- Support a
.azdignore file at the service source root using standard .gitignore syntax.
- Keep hardcoded security exclusions (
.azure/, .env, .env.*, .git/) always applied; not overridable via negation.
- Document behavior and add tests.
Feature Request
Add
.gitignore-style exclusion handling toazd code deployvia a user-customizable.azdignorefile.Background
Follow-up to the "Feature/code deploy zip upload" PR. From the review discussion:
Today, exclusions are hardcoded. Users need a way to customize what gets uploaded (e.g.,
node_modules/, build artifacts, local caches).Proposed
.azdignorefile at the service source root using standard.gitignoresyntax..azure/,.env,.env.*,.git/) always applied; not overridable via negation.