Task: Standardize Environment Variable Naming Conventions and Error Handling

[Luka-Loncar]

Description

We need to establish consistent organization-wide standards for environment variable naming and error handling. This issue is meant to facilitate discussion and agreement on these standards during the Tuesday planning meeting.
Current Situation

Environment Variable Naming:

• Currently using multiple different naming patterns across our codebase
• Examples of current variations (for discussion purposes):

#Some current patterns in use:
Simple prefix pattern: API_KEY, API_URL
Service-specific pattern: MASA_PROTOCOL_NODE_API
Extended patterns: MASA_PROTOCOL_NODE_API_PATH

• Need to agree on a consistent approach

Error Handling:

• Limited error handling currently in place (fetch_posts_from_api)
• Basic retry logic implemented in some places
• Opportunity to establish more robust standards

Discussion Points

1. Environment Variable Naming:

• What level of specificity do we need in our naming?
• How to handle service-specific variables?
• Considerations for maintainability and clarity
• Backward compatibility and migration approach

2. Error Handling Standards:

• What types of errors should we handle?
• Standard approaches for different scenarios
• Logging and error surfacing requirements
• Retry strategies

Goals

• Reach consensus on naming convention standards
• Define clear error handling patterns
• Create plan for implementing agreed-upon standards
• Establish documentation requirements

Questions for Tuesday Planning

• What naming patterns work best for our use cases?
• How detailed should our naming hierarchy be?
• What are our error handling priorities?
• How do we want to approach the migration?