timescale/Tiger Data - Fork Service
Fork an existing database to e.g. run tests on it
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| project_id | The project ID of your service | yes | — |
| service_id | The service ID of your service | yes | — |
| api_key | A Tiger Data API key in format publicKey:secretKey | yes | — |
| fork_strategy | The forking strategy to use | yes | — |
| cleanup | Whether to delete the fork after the workflow is complete | no | false |
| target_time | The timestamp to use for the fork format 2025-10-01T15:29:00Z | no | — |
| name | Custom name for the forked service (defaults to parent service name with "-fork" suffix) | no | — |
| cpu_millis | CPU allocation in milli-cores or 'shared' for shared resources (defaults to parent service allocation) | no | — |
| memory_gbs | Memory allocation in gigabytes or 'shared' for shared resources (defaults to parent service allocation) | no | — |
Outputs
| name | description |
|---|---|
| service_id | The ID of the forked service |
| name | The name of the forked service |
| host | The hostname/endpoint of the forked service |
| port | The port number of the forked service |
| initial_password | The initial password for the forked service |