api-test.http

### GitLab to GitHub Migrator API Tests
### Use with VS Code REST Client extension or similar tools
###
### Prerequisites:
### 1. Make sure the service is running: ./migrator -c config.json
### 2. Update @repoPath with actual repository path from your GitLab
### 3. Ensure GitLab and GitHub API tokens are configured in config.json
###
### If you get ECONNRESET errors, try using 127.0.0.1 instead of localhost

@baseUrl = http://localhost:8080
@baseUrlIPv4 = http://127.0.0.1:8080
@apiPrefix = /api/v1/migration

### Variables - Update these with your actual repository paths
@repoPath = sikatech/eshop/services/agent-service
@nestedRepoPath = sikatech/eshop/services/core-service
@githubOrg = sika365
@mappingFile = repositories.json

### Variables for GitLab API
@gitlabUrl = https://gitlab.sikapp.ir
@gitlabAdminToken = glpat-UMW2hQcyt8tPYz75fzri

##################################################
### 1. List All Repositories from GitLab
### Lists all repositories in the configured GitLab group
### including nested groups
##################################################
GET {{baseUrl}}{{apiPrefix}}/repositories
Content-Type: application/json

###

### Alternative: Use IPv4 if localhost doesn't work
GET {{baseUrlIPv4}}{{apiPrefix}}/repositories
Content-Type: application/json

###

##################################################
### 2. Get Repository Details
### Get detailed information about a specific repository
### Replace {{repoPath}} with actual repository path
##################################################
GET {{baseUrl}}{{apiPrefix}}/repositories/{{repoPath}}
Content-Type: application/json

###

##################################################
### 3. Get Migration Status for a Repository
### Check if a repository has been migrated to GitHub
### Returns: gitlab_path, github_name, migrated (bool), is_nested (bool)
##################################################
GET {{baseUrl}}{{apiPrefix}}/status/{{repoPath}}
Content-Type: application/json

###

##################################################
### 4. Migrate Single Repository (Dry Run)
### Test migration without actually creating repositories
### This will show what would be migrated without making changes
##################################################
POST {{baseUrl}}{{apiPrefix}}/repositories/{{repoPath}}/migrate
Content-Type: application/json

{
  "dry_run": true
}

###

##################################################
### 5. Migrate Single Repository (Actual Migration)
### ⚠️ WARNING: This will actually migrate the repository!
### Make sure you want to proceed before running this.
### 
### This will:
### - Create repository in GitHub
### - Migrate code (branches, tags, history)
### - Migrate issues, labels, milestones
### - Migrate merge requests as pull requests
### - Migrate wikis (if enabled)
##################################################
POST {{baseUrl}}{{apiPrefix}}/repositories/{{repoPath}}/migrate
Content-Type: application/json

{
  "dry_run": false
}

###

##################################################
### 6. Migrate All Repositories (Dry Run)
##################################################
POST {{baseUrl}}{{apiPrefix}}/migrate-all
Content-Type: application/json

{
  "dry_run": true
}

###

##################################################
### 7. Migrate All Repositories (Actual Migration)
##################################################
POST {{baseUrl}}{{apiPrefix}}/migrate-all
Content-Type: application/json

{
  "dry_run": false
}

###

##################################################
### 8. Export Repositories to JSON File
### Phase 1: Discovery - Export all GitLab repositories to JSON
### This creates a mapping file with GitLab to GitHub name mappings
### You can review and edit the JSON file before migration
##################################################

### Export repositories to default file
POST {{baseUrl}}{{apiPrefix}}/export
Content-Type: application/json

{
  "output_path": "{{mappingFile}}"
}

###

### Export repositories to custom file
POST {{baseUrl}}{{apiPrefix}}/export
Content-Type: application/json

{
  "output_path": "my-repositories.json"
}

###

##################################################
### 9. Import Repositories from JSON File
### Read repository mappings from a JSON file
### This validates the file and returns repository count
##################################################

### Import repositories from JSON file
POST {{baseUrl}}{{apiPrefix}}/import
Content-Type: application/json

{
  "input_path": "{{mappingFile}}"
}

###

##################################################
### 10. Migrate from JSON File (Two-Phase Approach)
### Phase 2: Migration - Migrate repositories from JSON file
### This reads the JSON file and migrates each repository
### The JSON file can be updated with migration status
##################################################

### Migrate from JSON file (Dry Run)
POST {{baseUrl}}{{apiPrefix}}/migrate-from-file
Content-Type: application/json

{
  "input_path": "{{mappingFile}}",
  "output_path": "{{mappingFile}}",
  "dry_run": true
}

###

### Migrate from JSON file (Actual Migration)
### ⚠️ WARNING: This will actually migrate repositories!
### Make sure you've reviewed the JSON file before running this.
POST {{baseUrl}}{{apiPrefix}}/migrate-from-file
Content-Type: application/json

{
  "input_path": "{{mappingFile}}",
  "output_path": "{{mappingFile}}",
  "dry_run": false
}

###

### Migrate from JSON file without updating the file
POST {{baseUrl}}{{apiPrefix}}/migrate-from-file
Content-Type: application/json

{
  "input_path": "{{mappingFile}}",
  "dry_run": false
}

###

##################################################
### 11. Test with Different Repository Paths
### Test nested repository paths
### Example: sikatech/eshop/services/core-service
### Will be mapped to: eshop-core-service (using last-group strategy)
##################################################

### Get nested repository details
GET {{baseUrl}}{{apiPrefix}}/repositories/{{nestedRepoPath}}
Content-Type: application/json

###

### Test migration with nested path (Dry Run)
POST {{baseUrl}}{{apiPrefix}}/repositories/{{nestedRepoPath}}/migrate
Content-Type: application/json

{
  "dry_run": true
}

###

### Get migration status for nested repository
GET {{baseUrl}}{{apiPrefix}}/status/{{nestedRepoPath}}
Content-Type: application/json

###

##################################################
### 12. Health Check
### Check if the service is running
##################################################
GET {{baseUrl}}/health
Content-Type: application/json

###

##################################################
### 13. Test Error Cases
##################################################

### Test with non-existent repository
GET {{baseUrl}}{{apiPrefix}}/repositories/non-existent/repo
Content-Type: application/json

###

### Test migration with invalid path
POST {{baseUrl}}{{apiPrefix}}/repositories/invalid/path/migrate
Content-Type: application/json

{
  "dry_run": true
}

###

### Test with empty request body (should use default dry_run=false)
POST {{baseUrl}}{{apiPrefix}}/migrate-all
Content-Type: application/json

{
}

###

##################################################
### 14. GitLab Maintenance Mode
### Enable/Disable GitLab maintenance mode
### Requires admin access token (PRIVATE-TOKEN)
##################################################

### Enable Maintenance Mode
PUT {{gitlabUrl}}/api/v4/application/settings?maintenance_mode=true&maintenance_mode_message=Maintenance
PRIVATE-TOKEN: {{gitlabAdminToken}}

###

### Disable Maintenance Mode
PUT {{gitlabUrl}}/api/v4/application/settings?maintenance_mode=false
PRIVATE-TOKEN: {{gitlabAdminToken}}

###