When adding units to charms that use peer relations, they don't see to be inheriting the default unit data for ingress-address, egress-subnet, private-address etc. in the relation data
I put together a demo charm (https://github.com/jnsgruk/charm-demo-peer-relation), if you build and deploy it, then scale it and watch the debug log, it outputs something similar to this when it is scaled up/down
```
Unit peer-relation-demo/0 can see the following data: KeysView({<ops.model.Unit peer-relation-demo/0>: {}, <ops.model.Application peer-relation-demo>: {'leader-ip': '10.1.215.247'}})
```
I added the same logger instruction to a pod_spec charm (mongodb-operator) to test the behaviour, and each of the units get data like the following on the peer relation by default:
```
mongodb/0 can see the following KeysView({<ops.model.Unit mongodb/0>: {'egress-subnets': '10.152.183.206/32', 'ingress-address': '10.152.183.206', 'private-address': '10.152.183.206'}, <ops.model.Application mongodb>: {}, <ops.model.Unit mongodb/2>: {'egress-subnets': '10.152.183.206/32', 'ingress-address': '10.152.183.206', 'private-address': '10.152.183.206'}, <ops.model.Unit mongodb/1>: {'egress-subnets': '10.152.183.206/32', 'ingress-address': '10.152.183.206', 'private-address': '10.152.183.206'}})
```
It seems that sidecar charms are not populated with the juju-info implicit relation fields
Line in the demo charm that is dumping the relation data: https:/ /github. com/jnsgruk/ charm-demo- peer-relation/ blob/29422d263b 20309d223b5020b 26363eae316c8d1 /src/charm. py#L74