agentuity-cli-cloud-env-pull
Pull environment variables from cloud to local .env.production file. Requires authentication. Use for Agentuity cloud platform operations
When & Why to Use This Skill
The agentuity-cli-cloud-env-pull skill automates the synchronization of environment variables between the Agentuity cloud platform and local development environments. By programmatically fetching cloud-stored configurations into a local .env.production file, it eliminates manual copy-pasting errors, ensures configuration consistency across teams, and streamlines the setup of production-ready local environments.
Use Cases
- Production Environment Mirroring: Quickly replicate cloud-based production settings to a local machine for accurate debugging and pre-deployment testing.
- Team Configuration Syncing: Enable team members to stay updated with the latest environment variables managed on the Agentuity platform without manual intervention.
- Automated CI/CD Preparation: Integrate into deployment pipelines to dynamically pull required secrets and variables before executing build or deployment scripts.
- Secure Secret Management: Maintain a single source of truth in the cloud while securely distributing environment variables to authorized local developers via authenticated CLI commands.
| name | agentuity-cli-cloud-env-pull |
|---|---|
| description | Pull environment variables from cloud to local .env.production file. Requires authentication. Use for Agentuity cloud platform operations |
| version | "0.0.104" |
| license | Apache-2.0 |
| allowed-tools | "Bash(agentuity:*)" |
| command | "agentuity cloud env pull" |
| tags | "slow requires-auth requires-project" |
Cloud Env Pull
Pull environment variables from cloud to local .env.production file
Prerequisites
- Authenticated with
agentuity auth login - Project context required (run from project directory or use
--project-id) - cloud deploy
Usage
agentuity cloud env pull [options]
Options
| Option | Type | Required | Default | Description |
|---|---|---|---|---|
--force |
boolean | No | false |
overwrite local values with cloud values |
Examples
Run pull command:
bunx @agentuity/cli env pull
Use force option:
bunx @agentuity/cli env pull --force
Output
Returns JSON object:
{
"success": "boolean",
"pulled": "number",
"path": "string",
"force": "boolean"
}
| Field | Type | Description |
|---|---|---|
success |
boolean | Whether pull succeeded |
pulled |
number | Number of items pulled |
path |
string | Local file path where variables were saved |
force |
boolean | Whether force mode was used |