Also I’m just wondering how do we keep upstream modules in our repo? They
are not submodules, so how is it organized?
Currently, we don't have any automatic tracking system for changes we apply
to the community/upstream modules, that could help us to re-apply them
during the sync. Only git or
Hi,
following our docs/workflow plus writing rspec tests for every new option
we add/modify in our manifests could help with regressions. For example:
- we add new keystone config option in openstack::keystone class -
keystone_config {'cache/backend': value =
Fuelers
I am writing that we had a really sad incident - we noticed that after we
merged upstream keystone module we lost modifications (Change-Id:
Idfe4b54caa0d96a93e93bfff12d8b6216f83e2f1
https://review.openstack.org/#/q/Idfe4b54caa0d96a93e93bfff12d8b6216f83e2f1,n,z)
for memcached dogpile
