Answer»
- Avoid project renames. If projects need to be renamed, do so concurrently across development, QA, stage and production systems before the next DEPLOYMENT.
- Operations on environment specific resources are best filtered out at import time. ADMINISTRATORS may define these resources (referenced in the import file) in the target system before starting the import process. Alternatively, new environment-specific resources may be DEPLOYED and customized for the environment after the import.
- Operational resources controlled by the operator should not be impacted by the import. A naming convention or a dedicated folder could be used to identify such resources during import.
- When the customization file contains the customizations of all project resources in a single file, apply customizations only to resources that are imported. An alternative is to preserve environment values on import and only apply customizations to resources that are added during import.
- At export-time, the exporter NEEDS to know if resources have been deleted, renamed, or moved; and if there have been project reorganizations of artifacts since the last export. If yes, complete deployment should be done. If no, the exporter can select only those resources that need to be exported and an INCREMENTAL deployment can be done.
|
