> However, is it correct for Apache/1 to have the config from vhost_rdata if
its associated dummy-vhost/1 hasn't actually started up yet?
I don't think it is. It definitely feels like a use-case for unit data bags with a container-scoped relation. I think this example is useful for demonstration purposes only.
We could just say that this is a valid sequence of events:
> However, is it correct for Apache/1 to have the config from vhost_rdata if
its associated dummy-vhost/1 hasn't actually started up yet?
I don't think it is. It definitely feels like a use-case for unit data bags with a container-scoped relation. I think this example is useful for demonstration purposes only.
We could just say that this is a valid sequence of events:
1) relation-created;
2) relation-changed (app data);
3) relation-joined;
4) relation-changed (remote unit data).
And then charms and the framework itself would have to handle that situation gracefully for subordinates.
It is quite specific to container-scoped relations because it seems like for global-scoped ones this sequence should always be the case:
1) relation-created;
2) relation-joined;
3) relation-changed (app or unit data).
I may be wrong in my assumption because the relation-created feature isn't there yet.
What do you think?