agentuity-cli-cloud-secret-pull
Pull secrets 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-secret-pull skill automates the secure retrieval of sensitive environment variables from the Agentuity cloud platform to local .env.production files. It streamlines DevOps workflows by ensuring local environments are perfectly synchronized with cloud-stored secrets, reducing manual configuration errors and enhancing security posture.
Use Cases
- Automated Environment Synchronization: Quickly update local .env.production files with the latest cloud-stored secrets to ensure environment parity.
- Secure Credential Management: Eliminate the risks associated with manual copy-pasting of sensitive API keys and database credentials by using an authenticated CLI pull.
- DevOps Pipeline Integration: Incorporate secret retrieval into local deployment scripts or CI/CD pre-flight checks to verify configuration readiness.
- Project Onboarding: Simplify the setup process for new developers by allowing them to pull necessary production secrets through a single authenticated command.
| name | agentuity-cli-cloud-secret-pull |
|---|---|
| description | Pull secrets 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 secret pull" |
| tags | "slow requires-auth requires-project" |
Cloud Secret Pull
Pull secrets 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 secret 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 secret pull
Use force option:
bunx @agentuity/cli secret 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 secrets were saved |
force |
boolean | Whether force mode was used |