You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix values init --force behavior and add --skip-defaults flag
**Problem:**
- `values init --force` was creating invalid configurations by skipping required fields without defaults
- No option to skip fields with defaults entirely
**Solution:**
1. **Fixed --force behavior:**
- ✅ Use defaults automatically (no prompt)
- ✅ Still prompt for required fields without defaults (ensures valid config)
- ✅ Skip optional fields without defaults
- ✅ Never create invalid configurations
2. **Added --skip-defaults flag:**
- Skip all fields with default values entirely
- Can be combined with --force for ultimate speed
**New Behaviors:**
```bash
# Normal: Full interactive
helm values-manager values init --env prod
# Fixed --force: Safe + fast
helm values-manager values init --env prod --force
# → Uses defaults, prompts only for required fields without defaults
# New --skip-defaults: Skip defaults entirely
helm values-manager values init --env prod --skip-defaults
# → Skip defaults, prompt for everything else
# Combined: Maximum speed
helm values-manager values init --env prod --force --skip-defaults
# → Skip defaults, use where needed, prompt only for required without defaults
```
**Testing:**
- Added comprehensive tests for all flag combinations
- Updated existing tests to expect new safe behavior
- All 121 tests passing with 81% coverage
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Support loading `.env` file for ENV based secrets
2
+
- May be an option 2 specify schema path?
2
3
- Support to add schemas without interaction.
3
-
- value from multiple options
4
-
-
4
+
- Updating schema or schema migration. Cases like default value change / path change / deletion etc.
5
+
- value from multiple options (eg: value should be one of [a,b,c])
6
+
- Nice to have: completion based on resources in json files.
7
+
8
+
bugs
9
+
- While using `helm-values-manager values init` or `helm-values-manager values set` what is the difference between n/skip both seems to do same functionality
10
+
11
+
-`helm-values-manager values init -f` is only supposed to skip default value's prompt and ask others. But looks like it add the default values in to the values json file while not prompting others. Either -f should skip the defaults all together and ask about others. Or we should add new option to skip defaults. What do you think?
0 commit comments