bluebricks-co/Bricks CLI Action
Manages Bricks CLI operations for Infrastructure as Code
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Maintainedlast commit Apr 10, 2025
- License
- Apache 2.0
Pinned Snippet
uses: bluebricks-co/bricks-action@db4645c781806df99a5be667a2cde1911b14c46b # v1.2.0tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| command | Primary Bricks command (bprint, bp, clouds, env, install, publish, updateci, etc) | yes | — |
| subcommand | Subcommand for the primary command (publish, bump, prepare, etc) | no | — |
| package | Package name for operations that require it | no | — |
| version | Version specification for version-related commands | no | — |
| file | Path to a YAML manifest file for the install command (used with -f flag) | no | — |
| env | Environment slug as the deployment target (used with install command) | no | — |
| plan-only | Will create a deployment plan only without executing the deployment (used with install command) | no | false |
| set-slug | Set deployment slug for install command | no | — |
| config-file | Path to Bricks config file | no | $HOME/.bricks/config.yaml |
| api-key | Bricks API key for authentication | yes | — |
| api-url | Bricks API URL for communication | no | https://api.bluebricks.co |
| props | JSON string of properties | no | — |
| props-file | Path to JSON properties file for install command | no | — |
| bump_type | Type of version bump to apply (major, minor, patch) | no | — |
| src | Source path for blueprint operations | no | . |
| artifacts-folder | Path to artifacts folder | no | bluebricks/packages |
| blueprints-folder | Path to blueprints folder | no | bluebricks/blueprints |
| artifact-bump | Version bump type for packages | no | patch |
| blueprint-bump | Version bump type for blueprints | no | patch |
| output | Output format (ascii or json) | no | ascii |
| base | Base branch for git diff | no | origin/main |
| head | Head Git reference for updateci command comparison | no | HEAD |
| flags | Additional flags to be added to any command (e.g., --dry) | no | — |
Outputs
| name | description |
|---|---|
| has_changes | Boolean indicating whether any changes were detected and applied |
| changes_summary | Formatted summary of all version changes made to artifacts and blueprints |
| dependency_graph | Visual representation of the dependency relationships between updated components |
| deployment_plan | Detailed deployment plan for install command |
| plan_id | Unique identifier for the generated deployment plan |
| artifacts_plan_ids | Comma separated list of artifacts plan IDs in format <artifact_name>:<plan_id> |
| deployment_id | Identifier for the deployment |
| deployment_svg | Base64 encoded SVG visualization of the deployment |
| error | Error message if the command failed |