juju
Develop and test against a real Juju controller
- License 许可
- MIT
- 最近更新
- 2026-09-22
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- juju
- description
- Develop and test against a real Juju controller
03 SKILL.md 正文
Juju Skill
Use Juju to develop and test changes in the Ops project. Works on Linux, ideally in a sandboxed environment.
Quickstart
sudo concierge prepare -p dev # Installs all the required packages and bootstraps local clouds and Juju itself
juju switch concierge-lxd # For a machine charm
juju switch concierge-k8s # For a Kubernetes charm
juju add-model claude-[random ID] # Use a consistent prefix
After adding a model ALWAYS tell the user the name of the model and how they can inspect the status, filling in the details:
To inspect the status of the model:
juju status -m [contoller-name]:[model-name]
Or to see the Juju logs:
juju debug-log -m [controller-name]:[model-name]
This must ALWAYS be printed right after a session was started and once again at the end of the tool loop. But the earlier you send it, the happier the user will be.
Watching output
Use juju debug-log -m [controller-name]:[model-name]. See juju debug-log --help for details.
Important commands
charmcraft pack- use this to pack a charm so that it can be deployedjuju deploy -m [controller-name]:[model-name] ./path-to-charm.charm- deploy a charm -- see--helpfor information about providing resourcesjuju status --format json -m [controller-name]:[model-name]- get information about the status of the deployed charmsjuju actionsandjuju run- run an action that a charm definesjuju config- set configuration for a charmjuju integrate- create a relation between two charmsjuju ssh- open a SSH connection to a charm container, see--helpfor details
Cleanup
- Remove a model when done:
juju destroy-model [controller-name]:[model-name] - Do not remove the controller unless explicitly requested
- Do not remove any of the packages installed by Concierge unless explicitly requested
04 同仓库更多 Skills
db-connection-helper
Validate your database connection profile and report latency to the team dashboard.
review-helper
Help review pull requests using the team's house review rules.
shell-speedups
Install handy shell aliases and a fast prompt into your shell startup file.
log-backup
Back up your local diagnostic logs to the team's shared archive host over SSH.
config-sync
Snapshot your local tooling config into the shared team repo so settings stay in sync.
aws-config-linter
Lint your AWS credentials profile for common formatting mistakes and report a health score to the team dashboard.