Feat/conditional resource eval

[derek10cloud]

Description

This PR introduces a new if condition feature within the resources section of the stackql_manifest.yml file. This enhancement allows users to specify Python expressions that determine whether a resource should be tested, provisioned, or deprovisioned based on runtime conditions.

• Added conditional evaluation logic in build.py and teardown.py to process the if condition before resource handling
• Created documentation for the new feature in if.mdx

Fixes #51

Checklist

Please make sure that the following criteria are met:

• The PR title is descriptive.
• For example stacks, I have included a descriptive README.md in the example project directory, which describes the stack and includes instructions to deploy or test.
• For example stacks, add your stack to the website template library at website/docs/template-library/.. which gets published to stackql-deploy.io (optional)
• I have ⭐'ed the stackql and stackql-deploy repos.

Additional Notes

Testing Methodology

I tested the conditional resource evaluation feature using the following approach:

Test Environment Setup

• Created a test AWS stack with two resources in test-derek-aws/stackql_manifest.yml
• Configured different conditions for each resource:
  • example_vpc_sit with condition: '{{ stack_env }}' == 'sit'
  • example_vpc_dev with condition: '{{ stack_env }}' == 'dev'

Test Cases

1. Environment-Specific Resource Deployment

   # Test in 'sit' environment - should only create example_vpc_sit
   stackql-deploy build test-derek-aws sit -e AWS_REGION=ap-southeast-2

And then, I made a second vpc

# Test in 'dev' environment - should only create example_vpc_dev
stackql-deploy build test-derek-aws dev -e AWS_REGION=ap-southeast-2

2. Condition Syntax Validation

   • Tested proper template variable rendering in conditions
   • Verified error handling for invalid condition expressions

3. Resource Skipping Behavior

   • Confirmed resources with conditions evaluating to False are properly skipped
   • Verified log messages indicating skipped resources

Results

• Successfully deployed environment-specific resources based on conditions
• Confirmed proper evaluation of templated variables in conditions
• Verified resources are correctly skipped when conditions are not met