[Checkins] [zopefoundation/keas.build] 4433c0: feature: implemented a new argument `vars` in depl...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/zopefoundation/keas.build
  Commit: 4433c035a9b4fdbf073eb1ea24b8b8e582412138
      https://github.com/zopefoundation/keas.build/commit/4433c035a9b4fdbf073eb1ea24b8b8e582412138
  Author: Roger Ineichen <dev at projekt01.ch>
  Date:   2013-10-23 (Wed, 23 Oct 2013)

  Changed paths:
    M CHANGES.txt
    M setup.py
    M src/keas/build/build.py
    M src/keas/build/index.txt

  Log Message:
  -----------
  feature: implemented a new argument `vars` in deployment template section. The
new `vars` argument can get used for define a release template section. If
defined, the build process will apply all arguments from this section as they
would be a a part of the project section. This allows to inherit a large
amount of arguments in a project definition instead of define them in
each project. This is usefull if you have a stage and many production variants
and the instance uses config data like a database setup and you need to
share them. For such a usecase you can simply define a stage and production
section and define all shared arguments and use the right `vars` section in
your product deployment setup. See the memcached sample in index.txt

Note, this new product deployment template `vars` argument could be a problem
for your existing setup if you use a vars argument with a value similar then
a section name defined in your section template.


  Commit: 487169b88748d07c1d4b06cf124bb5af5edd2ac6
      https://github.com/zopefoundation/keas.build/commit/487169b88748d07c1d4b06cf124bb5af5edd2ac6
  Author: Roger Ineichen <dev at projekt01.ch>
  Date:   2013-10-23 (Wed, 23 Oct 2013)

  Changed paths:
    M CHANGES.txt
    M MANIFEST.in
    M setup.py
    M src/keas/build/base.py
    M src/keas/build/package.py

  Log Message:
  -----------
  implemented a new argument `vars` in deployment template section

feature: implemented a new argument `vars` in deployment template
section. The
new `vars` argument can get used for define a release template section.
If
defined, the build process will apply all arguments from this section as
they
would be a a part of the project section. This allows to inherit a large
amount of arguments in a project definition instead of define them in
each project. This is usefull if you have a stage and many production
variants
and the instance uses config data like a database setup and you need to
share them. For such a usecase you can simply define a stage and
production
section and define all shared arguments and use the right `vars` section
in
your product deployment setup. See the memcached sample in index.txt

Note, this new product deployment template `vars` argument could be a
problem
for your existing setup if you use a vars argument with a value similar
then
a section name defined in your section template.


  Commit: 3a32c63f42f567bc1ee3af34a3470cd63c627452
      https://github.com/zopefoundation/keas.build/commit/3a32c63f42f567bc1ee3af34a3470cd63c627452
  Author: Roger Ineichen <dev at projekt01.ch>
  Date:   2013-10-23 (Wed, 23 Oct 2013)

  Log Message:
  -----------
  Merge branch 'master' of https://github.com/zopefoundation/keas.build

Conflicts:
	CHANGES.txt
	setup.py


Compare: https://github.com/zopefoundation/keas.build/compare/626f3bf7bb1b...3a32c63f42f5