Relations-only config will not deploy
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-deployer |
Confirmed
|
High
|
Unassigned | ||
Bug Description
Previously, juju-deployer (juju-core branch) would deploy a config that contained only relations. Now it appears that relations are always verified against services and charms. The deployment fails if the config does not define any services.
At the very least, it would be helpful to have an override that allows the checks to be disabled.
It would be even better to have juju-deployer perform the checks against the *running environment*. That would allow still allow deployer to establish relations with services managed by other means.
The use case for this is a CI system which separates deployments and relations into separate tasks. This gives us more fine-grained reporting on where a deployment fails, and allows us to establish relations in phases.
| Kapil Thangavelu (hazmat) wrote | #1 |
| Changed in juju-deployer: | |
| status: | New → Confirmed |
| tags: | added: post-py-drop |
| Changed in juju-deployer: | |
| importance: | Undecided → High |
i'd still like the checks, else the config is invalid, and deployer should report that rather than failing mid deployment. The fix would be to have the checks take int account the env services with the deployment config services. Which t should satisfy your use case while retaining validation.