# Managing Repositories in AIQ

# Managing Repositories in AIQ

Repositories store or exchange assets used by AIQ workflows, such as scripts, test data, evidence, and integration files. Keep repository definitions consistent across environments so tests remain portable and supportable.

## Recommended guidance

- Use clear repository names that identify the environment, purpose, and owner.
- Document repository type, endpoint, path, credentials, retention expectations, and cleanup process.
- Use secured credentials or roles and avoid shared personal accounts.
- Separate development, staging, and production-like repositories when possible.
- Validate read/write access with small non-sensitive files before using the repository in a test.

## Maintenance workflow

1. Review repository usage before changing or removing an entry.
2. Update dependent tests, Service Suite flows, or CI/CD jobs when endpoint details change.
3. Monitor storage growth and remove obsolete artifacts according to retention policy.
4. Record ownership and renewal dates for credentials or certificates.

*Last updated: October 9, 2026*