# Repositories # Repositories Overview in AIQ Use this overview to understand how repositories support AIQ scenario, resource, and test asset management. ## What changed in this article - Converted the short “Repositories” page into an overview that points to configuration and operational usage. - Clarified that repositories should have clear ownership, access control, branch/path strategy, and review practices. - Added checks for pull behavior, asset visibility, dependency paths, and avoiding sensitive files in repositories. ## Validation workflow 1. Identify what assets belong in the repository and who owns them. 2. Confirm repository access, branch/path strategy, and permissions before connecting it to AIQ. 3. Validate that scenarios can read required assets after a pull and that no secrets are exposed. **Review note:** This page now acts as an overview while the repository configuration page covers setup details. --- Last updated: October 5, 2026 If you have feedback on this topic, contact . # Set Up a Repository Connection in AIQ ## Recommended guidance Set up repository connections in AIQ when tests, services, data files, or reusable assets need to come from controlled source control. The connection should be tied to a clear project, branch strategy, and access model. ## Before setup - Confirm repository URL, provider, branch, folder path, and target AIQ project. - Validate network, proxy, firewall, DNS, and certificate access from the AIQ host. - Use approved Git credentials, tokens, or SSH keys with the minimum required access. - Confirm whether AIQ should read only or also write back to the repository. ## Validation workflow 1. Create or update the repository connection in Global Options. 2. Test connectivity and confirm the expected files appear. 3. Run a small Scenario Editor or Service Suite smoke test that uses repository content. 4. Document repository owner, branch policy, credential rotation, and rollback expectations. *Last updated: October 6, 2026* # Configure Repositories in AIQ Use this article when connecting AIQ to Git, SVN, or other approved repositories for scenario, resource, and test asset storage. ## What changed in this article - Renamed the page to current AIQ terminology and shortened the title. - Updated repository guidance around Git/SVN configuration, credentials, tokens, SSH keys, pull behavior, and File Explorer usage. - Added security checks for credential handling, repository ownership, branch strategy, permissions, and avoiding secrets in committed files. ## Validation workflow 1. Confirm the repository type, URL, branch/path strategy, owner, and authentication method before adding it to AIQ. 2. Add or update the repository from the approved AIQ repository workflow and validate connectivity with a pull. 3. Review permissions and test that scenario/resource files are visible without exposing credentials or unrelated repository content. **Review note:** This page now focuses on secure repository setup and operational validation. --- Last updated: October 5, 2026 If you have feedback on this topic, contact . # 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* # Configure a Git Repository in AIQ ## Recommended guidance Configure Git repositories in AIQ so scenarios, service assets, data files, and shared resources can be maintained through controlled version history. Repository access should use approved credentials or keys and should avoid storing secrets in source control. ## Before configuration - Confirm the repository URL, branch, folder path, and intended AIQ project or workspace. - Use a service account, token, or SSH key approved for automation. - Grant the minimum permissions needed for read or write operations. - Confirm network, proxy, certificate, and firewall access from the AIQ host. - Define who owns repository updates and review approvals. ## Validation checklist 1. Test repository connectivity from AIQ. 2. Confirm the expected branch and files appear in the project. 3. Run a small Scenario Editor or Service Suite smoke test that uses the repository content. 4. Document branch strategy, credential rotation, and rollback expectations. *Last updated: October 6, 2026* # Legacy SVN Repository Configuration **Last reviewed:** September 24, 2026 This article is retained as a legacy reference for teams that still maintain SVN-backed AIQ assets. ## Recommended guidance - Use Git-based repository workflows where available for current AIQ projects. - Keep SVN access limited to environments that still depend on historical repositories. - Store repository credentials securely and rotate them according to your organization policy. ## Validation workflow 1. Verify that the project still requires SVN before configuring it. 2. Create or validate the repository path and user permissions outside AIQ. 3. Connect the repository from AIQ and run a small save or sync test. **Note:** SVN is legacy guidance. Do not use it as the default repository recommendation for new AIQ implementations. --- Last updated: September 24, 2026 If you have feedback on this topic, contact . # Configure an S3 Repository in AIQ # Configure an S3 Repository in AIQ Use an Amazon S3 repository when AIQ needs to read or write test assets, files, evidence, or integration payloads in AWS object storage. Corrected the title spelling and updated the page around current repository and AWS security practices. ## Configuration checklist - Confirm AWS account, region, bucket name, prefix/path, encryption, and lifecycle policy. - Prefer IAM roles, instance profiles, or temporary credentials over static access keys. - Grant only the required S3 actions for the specific bucket and prefix. - Use server-side encryption and customer-approved retention settings. - Document ownership, cost tags, cleanup policy, and access-review cadence. ## Validation workflow 1. Validate read/write access with a small non-sensitive test file. 2. Run the AIQ workflow that uses the S3 repository. 3. Review AWS and AIQ logs for permission, region, bucket, path, or encryption errors. 4. Confirm lifecycle or cleanup rules do not remove required evidence too early. *Last updated: October 9, 2026* # Configure an FTP Repository in AIQ # Configure an FTP Repository in AIQ Use FTP repositories only when required by a customer environment. Prefer SFTP, HTTPS, or cloud repository options when security policy allows, because standard FTP does not encrypt credentials or file contents. ## Configuration checklist - Confirm host, port, username, target folder, passive/active mode, and firewall requirements. - Use a dedicated repository account with the minimum folder permissions required. - Separate input, output, archive, and error folders when the workflow requires them. - Document retention, cleanup, and file-naming expectations. - Do not use FTP for sensitive data unless the customer has explicitly approved the risk. ## Validation workflow 1. Test connectivity from the AIQ environment or node that will access the repository. 2. Upload and download a small non-sensitive test file. 3. Run the AIQ workflow that reads or writes the repository. 4. Review logs for authentication, permission, path, timeout, or firewall errors. *Last updated: October 9, 2026* # Configure an SFTP Repository in AIQ # Configure an SFTP Repository in AIQ Configure an SFTP repository when AIQ needs to exchange files with a controlled external location. Use secure credentials, least-privilege access, and a clear folder structure for test assets and outputs. ## Configuration checklist - Confirm the SFTP host, port, username, authentication method, and target folder. - Use SSH keys or secured credentials according to the customer security policy. - Grant the AIQ account only the folder permissions required by the workflow. - Separate input, output, archive, and error folders when the process requires them. - Document file naming, retention, and cleanup expectations. ## Validation workflow 1. Test connectivity from the AIQ environment or node that will access the repository. 2. Upload and download a small non-sensitive test file. 3. Run the AIQ workflow that reads or writes the repository. 4. Review logs for authentication, permission, path, or timeout errors. *Last updated: October 8, 2026* # Repository Troubleshooting # Repository FAQ # GitHub - Authenticating with SAML single sign-on