🌍 Environment Management

This section defines how environments are structured and used across our integration projects. Clear environment separation ensures safe development, reliable testing, and secure production operations.

🧭 Environment Overview

We operate with four main environments, each serving a specific purpose in the development and delivery lifecycle:

Environment	Code	Purpose
Development	DEV	Used by developers for building and unit testing integration components. May contain mock or partial data.
Integration	INT	Used for integration testing across systems. Shared by development teams to validate end-to-end flows.
User Acceptance	REC	Used for user acceptance testing (UAT) and validation by business users and non-production consumers. Mirrors production logic.
Production	PRD	Live environment used by end users and systems in production. Must be stable, secure, and auditable.

🔐 Environment Isolation

• Each environment is logically and physically isolated.
• No cross-environment access is allowed unless explicitly authorized.
• Secrets, credentials, and configurations must be environment-specific.
• Shared resources (e.g., Key Vaults) must be handled with care to avoid breaking other environments.

🧪 Testing Strategy

• All changes must be tested in DEV and validated in INT before being promoted to REC or PRD.
• REC is the only environment where business users perform validation.
• PRD deployments must follow the release process and approval workflow.

🧩 Environment Naming in Resources

Environment codes (dev, int, rec, prd) are used in resource names to clearly identify their scope.
Example:

• adfpimimportdev → Azure Data Factory for the pimimport project in DEV
• stojdeaccessprd → Storage Account for jdeaccess in PRD

📌 Best Practices

• Use lowercase for environment codes in resource names.
• Avoid hardcoding environment-specific values in code; use configuration files or parameterization.
• Document any environment-specific behavior or constraints in the project documentation.

🧠 Environment consistency is key to reliable deployments and smooth collaboration. Please follow these guidelines to avoid conflicts and ensure traceability.