Revert "feat: Improve add-deployment Command Tests and Coverage"

This reverts commit 52755c1.

Author: ritwik-g

docs/ADRs/006-helm-style-logging.md

@@ -31,12 +31,6 @@ class HelmLogger:
         if args:
             msg = msg % args
         print("Error: %s" % msg, file=sys.stderr)
-
-    @staticmethod
-    def warning(msg: str, *args: Any) -> None:
-        if args:
-            msg = msg % args
-        print("Warning: %s" % msg, file=sys.stderr)
 ```
 
 ### 2. Key Design Decisions
@@ -45,7 +39,6 @@ class HelmLogger:
    - Use stderr for all output
    - Prefix debug messages with "[debug]"
    - Prefix error messages with "Error:"
-   - Prefix warning messages with "Warning:"
    - Control debug output via HELM_DEBUG environment variable
 
 2. **Performance Optimization**
@@ -74,7 +67,6 @@ def some_function():
         logger.debug("Success!")
     except Exception as e:
         logger.error("Failed: %s", str(e))
-    logger.warning("Something unexpected happened")
 ```
 
 ## Consequences
@@ -103,7 +95,7 @@ def some_function():
 ### Negative
 1. **Limited Flexibility**
    - Fixed output format
-   - Limited log levels (debug/warning/error)
+   - No log levels beyond debug/error
    - No log file support
 
 2. **Global State**
@@ -121,12 +113,6 @@ def test_debug_output():
          mock.patch('helm_values_manager.utils.logger.sys.stderr', stderr):
         logger.debug("Test message")
         assert stderr.getvalue() == "[debug] Test message\n"
-
-def test_warning_output():
-    stderr = StringIO()
-    with mock.patch('helm_values_manager.utils.logger.sys.stderr', stderr):
-        logger.warning("Test warning")
-        assert stderr.getvalue() == "Warning: Test warning\n"
 ```
 
 2. **Integration**
@@ -136,5 +122,4 @@ def validate(self):
     logger.debug("Validating PathData for path: %s", self.path)
     if not self.is_valid():
         logger.error("Invalid PathData: %s", self.path)
-    logger.warning("PathData validation completed with warnings")
 ```

docs/ADRs/011-command-structure-for-deployments.md

@@ -78,10 +78,3 @@ For new ADRs, use the [ADR template](adr-template.md) as a starting point.
 - **Decision**: Implement configuration comparison and smart merging with multiple strategies
 - **Impact**: Simplifies configuration updates and reduces risk of missing required changes
 - **Dependencies**: ADR-001
-
-### [ADR-011: Command Structure for Deployments and Backends](011-command-structure-for-deployments.md)
-- **Status**: Accepted
-- **Context**: Need for intuitive command structure for managing deployments with multiple backends and auth types
-- **Decision**: Implement nested subcommand structure for deployment, backend, and auth configuration
-- **Impact**: Improves user experience, discoverability, and maintainability
-- **Dependencies**: ADR-001

docs/ADRs/README.md

@@ -174,31 +174,6 @@ Benefits:
 - Automatic file locking
 - Configuration backup support
 
-#### Command Structure for Deployments and Backends
-
-The command structure for managing deployments and backends follows a nested subcommand pattern (see [ADR-011](../ADRs/011-command-structure-for-deployments.md)):
-
-```
-helm values add-deployment [name]
-
-helm values add-backend [backend] --deployment=[name] [backend_options]
-  - helm values add-backend aws --deployment=prod --region=us-west-2
-  - helm values add-backend azure --deployment=prod --vault-url=https://myvault.vault.azure.net
-  - helm values add-backend gcp --deployment=prod --project-id=my-project
-  - helm values add-backend git-secret --deployment=prod
-
-helm values add-auth [auth_type] --deployment=[name] [auth_options]
-  - helm values add-auth direct --deployment=prod --credentials='{...}'
-  - helm values add-auth env --deployment=prod --env-prefix=AWS_
-  - helm values add-auth file --deployment=prod --auth-path=~/.aws/credentials
-  - helm values add-auth managed-identity --deployment=prod
-```
-
-This structure:
-- Separates the concerns of creating a deployment, configuring a backend, and setting up authentication
-- Uses subcommands to provide context-specific options and help text
-- Follows a natural workflow of first creating a deployment, then adding backend and auth configuration
-
 ### 4. Storage Backends
 
 The `ValueBackend` interface defines the contract for value storage:
@@ -227,8 +202,6 @@ Implementations:
 - Azure Key Vault Backend
 - Additional backends can be easily added
 
-For a comprehensive overview of supported backends, authentication types, and backend configurations, see [Backends and Authentication Types](backends-and-auth.md).
-
 ### 5. Schema Validation
 
 The configuration system uses JSON Schema validation to ensure data integrity and consistency: