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
refactor: update PathData validation and ADR status
- Move required value validation into PathData.validate() loop
- Add environment context to validation error messages
- Add tests for PathData serialization methods
- Mark ADR-005 (Unified Backend Approach) as Accepted
- Mark ADR-007 (Sensitive Value Storage) as Accepted
- Fix ADR-007 number in title
- Update README.md to reflect ADR status changes
This change improves error messages by including environment context
and keeps validation close to the data it validates. PathData now
has 100% test coverage.
Copy file name to clipboardExpand all lines: docs/ADRs/005-unified-backend-approach.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
# ADR-005: Unified Backend Approach for Value Storage
2
2
3
3
## Status
4
-
Proposed
4
+
Accepted
5
5
6
6
## Context
7
7
Currently, the Value class handles two distinct storage types: local and remote. This creates a split in logic within the Value class, requiring different code paths and validation rules based on the storage type. This complexity makes the code harder to maintain and test.
Copy file name to clipboardExpand all lines: docs/ADRs/007-sensitive-value-storage.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
-
# ADR 0002: Sensitive Value Storage
1
+
# ADR 007: Sensitive Value Storage
2
2
3
3
## Status
4
-
Proposed
4
+
Accepted
5
5
6
6
## Context
7
7
The helm-values-manager needs to handle both sensitive and non-sensitive configuration values. While non-sensitive values can be stored directly in the configuration files, sensitive values require special handling to ensure security.
0 commit comments