garden-cli
Advanced tools
Changelog
v0.3.0 (2018-07-10)
${local.platform}
template key (1c6d4927)env
key to specify env vars for containers (9fa0cb8d)Any existing garden.yml files with the build.command
key set need
to be updated to provide an array of strings as a command, as opposed to
a simple string.
Existing metadata namespaces will have to be manually cleaned up. We suggest resetting local k8s clusters after upgrading.
The tests[].variables
config key has been removed from the
garden.yml
configuration file schema.
<a name="v0.2.0"></a>
Changelog
v0.2.0 (2018-06-27)
ctx.getStatus()
(#134) (d2227210)Module.getVersion()
(6491678e)npm run dev
after package.json changes (8bd62173)processModules()
(b0eb86e7)The following CLI commands have now been renamed, and any scripts
using them need to be updated accordingly:
config delete
-> delete config
config get
-> get config
config set
-> set config
environment configure
-> init environment
environment destroy
-> delete environment
status
-> get status
Existing garden.yml files will need to be updated if they use the project.global key.
<a name="v0.1.2"></a>
Changelog
v0.1.0 (2018-05-31)
env config
command (8cb65120)This includes some changes to the project schema and how it is resolved,
as well as how the main Garden
class is instantiated. The Garden
class is now called with an environment name, which is then fixed for
the session. The env configuration is resolved by merging the specific
environment configuration with a global configuration specified on the
new global
key in the project config. The schema for the providers
key also different - its keys should now match plugin names, and
contain configuration for those plugins.