Environments

Satélite API supports multiple deployment environments with distinct configurations for production operations and development testing.

Available Environments

Satélite API maintains two primary deployment environments:

Production

Environment: ProductionURL: https://sateliteappapi.azurewebsites.netPurpose: Live production operations with real business dataCharacteristics:

High availability configuration
Auto-scaling enabled
Production database connections
Enhanced security and monitoring
Minimal logging for performance

Testing

Environment: QualityURL: https://sateliteappapi-test.azurewebsites.netPurpose: Development, testing, and QA validationCharacteristics:

Test database connections
Detailed logging enabled
Rapid deployment cycles
Isolated from production data
Lower resource allocation

Environment Configuration

The active environment is controlled by the ASPNETCORE_ENVIRONMENT variable, which determines which configuration files are loaded and how the application behaves.

Setting the Environment

# Set via Azure CLI
az webapp config appsettings set \
  --name sateliteappapi \
  --resource-group satelite-rg \
  --settings ASPNETCORE_ENVIRONMENT="Production"

Environment Values

Production Environment

Value: ProductionUsed for:

Production Azure Web App (sateliteappapi.azurewebsites.net)
Live customer-facing operations
Real business data processing

Configuration file: appsettings.Production.json

launchSettings.json:12-21

"SateliteApi": {
  "commandName": "Project",
  "dotnetRunMessages": true,
  "launchBrowser": true,
  "launchUrl": "graphql",
  "applicationUrl": "https://localhost:7251",
  "environmentVariables": {
    "ASPNETCORE_ENVIRONMENT": "Production"
  }
}

Quality (Testing) Environment

Value: QualityUsed for:

Testing Azure Web App (sateliteappapi-test.azurewebsites.net)
QA and UAT testing
Development validation

Configuration file: appsettings.Quality.json

launchSettings.json:22-29

"IIS Express": {
  "commandName": "IISExpress",
  "launchBrowser": true,
  "launchUrl": "swagger",
  "environmentVariables": {
    "ASPNETCORE_ENVIRONMENT": "Quality"
  }
}

Development Environment

Value: DevelopmentUsed for:

Local development on developer machines
Debugging and development features enabled
Detailed error pages and diagnostics

Configuration file: appsettings.Development.json

Development environment is not deployed to Azure. It’s only for local development.

Environment-Specific Settings

Configuration File Structure

Configuration is loaded in this order:

Base Configuration

appsettings.json - Shared settings across all environments

Environment Override

appsettings.{Environment}.json - Environment-specific overrides

Azure App Settings

Azure Portal App Settings - Highest priority, overrides all files

Environment Variables

System environment variables - Can override any setting

Example Configuration Structure

{
  "Logging": {
    "LogLevel": {
      "Default": "Information",
      "Microsoft": "Warning"
    }
  },
  "AllowedHosts": "*",
  "Jwt": {
    "Issuer": "SateliteApi",
    "Audience": "SateliteApi"
  }
}

Database Connections by Environment

Each environment connects to separate database instances to maintain data isolation:

Production
Testing (Quality)

Connection Strings: Point to production SQL Server instances

SateliteConnection → Production Satélite DB
CajachicaConnection → Production Cajachica DB
AnticiposConnection → Production Anticipos DB
NexusConnection → Production Nexus DB
And all other production databases…

Retry Configuration: Enabled for BitacoraCumplimientoDBContext and NexusDBContext

Program.cs:274-280

builder.Services.AddPooledDbContextFactory<BitacoraCumplimientoDBContext>(
    options => options.UseSqlServer(builder.Configuration.GetConnectionString("SateliteConnection"),
        sqlOptions => sqlOptions.EnableRetryOnFailure(
            maxRetryCount: 5,                      
            maxRetryDelay: TimeSpan.FromSeconds(30),
            errorNumbersToAdd: null                 
        )));

Connection Strings: Point to test SQL Server instances

SateliteConnection → Test Satélite DB
CajachicaConnection → Test Cajachica DB
AnticiposConnection → Test Anticipos DB
NexusConnection → Test Nexus DB
And all other test databases…

Same Configuration: Uses identical retry logic and connection pooling as production

Test databases should mirror production schema but contain test data only.

Switching Between Environments

For Azure Deployment

Update App Setting

Change ASPNETCORE_ENVIRONMENT in Azure Portal:

Navigate to Web App > Configuration
Under Application settings, find ASPNETCORE_ENVIRONMENT
Change value to desired environment (Production or Quality)
Click Save

Update Connection Strings

Verify connection strings point to correct databases:

Go to Configuration > Connection strings
Update each connection string to target correct database
Click Save

Restart Application

Restart the Web App to apply changes:

az webapp restart \
  --name sateliteappapi \
  --resource-group satelite-rg

For Local Development

Visual Studio
Command Line
dotnet run

Open Properties/launchSettings.json
Locate the profile you want to use
Change ASPNETCORE_ENVIRONMENT value
Save and restart debugger

"SateliteApi": {
  "environmentVariables": {
    "ASPNETCORE_ENVIRONMENT": "Production"  // Change here
  }
}

Set environment variable before running:

# Windows
set ASPNETCORE_ENVIRONMENT=Quality
dotnet run

# Linux/Mac
export ASPNETCORE_ENVIRONMENT=Quality
dotnet run

Use the --environment flag:

dotnet run --environment Production
# or
dotnet run --environment Quality

Environment-Specific Behaviors

Logging Levels

Production

Minimal Logging

Errors and Critical only
Reduced console output
Performance optimized
Log to Application Insights

Testing

Detailed Logging

Information and Debug levels
Verbose console output
Request/response logging
Easier troubleshooting

GraphQL Features

Both environments share the same GraphQL configuration:

10-minute execution timeout
Automatic persisted queries disabled in production
Introspection enabled in testing
GraphQL playground available in testing only

Scheduled Jobs

Scheduled jobs run in both environments but with different schedules:

Production Schedule
Testing Schedule

// Anticipo/Reembolso: Daily at 9:00 AM
"0 0 9 * * ?"

// Bitacora Caducidad: Daily at 8:00 AM
"0 0 8 * * ?"

// Gestor: Daily at 6:00 AM
"0 0 6 * * ?"

Consider adjusting cron schedules for testing:

// More frequent for testing (every 15 minutes)
"0 */15 * * * ?"

// Or disable specific jobs in testing
// Comment out job registration in Program.cs

Security Considerations

Never share credentials between environmentsEach environment must have:

Separate database credentials
Different JWT signing keys
Unique API keys for external services
Isolated Azure resources

Production Security

Enable Azure AD authentication
Use Azure Key Vault for all secrets
Restrict CORS to specific origins
Enable Application Insights security monitoring
Configure Web Application Firewall (WAF)
Regular security audits and penetration testing

Testing Security

Use separate service principals
Limit access to test data only
Allow broader CORS for development
Use non-production API credentials
Regular cleanup of test data

Best Practices

Always Test First

Deploy and test all changes in the Quality environment before promoting to Production

Use Configuration Files

Store environment-specific settings in configuration files, not in code

Monitor Both Environments

Set up Application Insights for both Production and Quality to catch issues early

Automate Deployments

Use CI/CD pipelines to ensure consistent deployments across environments

Maintain Parity

Keep Testing environment as close to Production as possible in configuration and infrastructure

Environment Health Checks

Verify environment is correctly configured:

curl https://sateliteappapi.azurewebsites.net/graphql

# Should return GraphQL playground or schema

Troubleshooting

Wrong database being accessed

Symptom: Application connects to incorrect databaseSolution:

Verify ASPNETCORE_ENVIRONMENT is set correctly
Check connection strings in Azure Portal
Ensure configuration file naming matches environment exactly
Restart the application after changes

Environment variable not taking effect

Symptom: Changes to environment variables don’t applySolution:

Verify the variable is set in correct location (Azure App Settings)
Click Save in Azure Portal after changes
Restart the Web App
Check logs to confirm environment is loaded correctly

Configuration conflicts

Symptom: Unexpected configuration valuesSolution: Remember configuration priority order:

Environment variables (highest)
Azure App Settings
appsettings..json
appsettings.json (lowest)

Higher priority sources override lower ones.

Next Steps

Azure Setup

Learn how to deploy to Azure Web Services

Configuration

Configure connection strings and application settings

Get Started

Core Concepts

Deployment

Environments

Environments

Available Environments

Production

Testing

Environment Configuration

Setting the Environment

Environment Values

Environment-Specific Settings

Configuration File Structure

Example Configuration Structure

Database Connections by Environment

Switching Between Environments

For Azure Deployment

For Local Development

Environment-Specific Behaviors

Logging Levels

Production

Testing

GraphQL Features

Scheduled Jobs

Security Considerations

Best Practices

Environment Health Checks

Troubleshooting

Next Steps

Azure Setup

Configuration

Build docs developers (and LLMs) love

Get Started

Core Concepts

Deployment

​Environments

​Available Environments

Production

Testing

​Environment Configuration

​Setting the Environment

​Environment Values

​Environment-Specific Settings

​Configuration File Structure

​Example Configuration Structure

​Database Connections by Environment

​Switching Between Environments

​For Azure Deployment

​For Local Development

​Environment-Specific Behaviors

​Logging Levels

Production

Testing

​GraphQL Features

​Scheduled Jobs

​Security Considerations

​Best Practices

​Environment Health Checks

​Troubleshooting

​Next Steps

Azure Setup

Configuration

Build docs developers (and LLMs) love

Environments

Available Environments

Environment Configuration

Setting the Environment

Environment Values

Environment-Specific Settings

Configuration File Structure

Example Configuration Structure

Database Connections by Environment

Switching Between Environments

For Azure Deployment

For Local Development

Environment-Specific Behaviors

Logging Levels

GraphQL Features

Scheduled Jobs

Security Considerations

Best Practices

Environment Health Checks

Troubleshooting

Next Steps