Tools to work with wercker environments
npm i -g @apr/werckerenvtools
To avoid writing the api token directly in the command line, it can be read from the environment variable WERCKERENVTOOLS_TOKEN.
Example:
werckerenvtools export [organization] [application] [pipeline] --token [token] --include-application false > ENVIRONMENT
will export the environment variables of the pipeline to file called ENVIRONMENT
Organization, application and pipeline must exist.
include-application is optional and defaults to false but will include application envvars if true
Example:
werckerenvtools import [organization] [application] [pipeline] --token [token] --overwrite true --file ENVIRONMENT
will import the environment variables of the update pipeline from file called ENVIRONMENT
Organization, application and pipeline must exist.
overwrite is optional and defaults to false but will overwrite existing keys
Example:
werckerenvtools sync [organization] [application] [src-pipeline] [dst-pipeline] --token [token]
will sync the environment variables of the src pipeline to the dst pipeline
Organization, application and pipelines must exist.
overwrite is optional and defaults to false but will overwrite existing keys
Example:
werckerenvtools trim [organization] [application] [pipeline] --token [token]
Trims all environment variable keys in the pipeline that also exists in application or organization