You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ydbinstall.sh script uses environment variables ydb_buildtype, ydb_dryrun, ydb_gtm, ydb_group_restriction, ydb_keep_obj, ydb_lcase_utils, ydb_overwrite_existing, ydb_prompt_for_group, and ydb_verbose to drive its operation, corresponding to the environment variables gtm_buildtype, gtm_dryrun, gtm_gtm, gtm_group_restriction, gtm_keep_obj, gtm_lcase_utils, gtm_overwrite_existing, gtm_prompt_for_group, and gtm_verbose. The latter remain supported, with the proviso that if a ydb_ prefixed environment and the corresponding gtm_ prefixed environment variable are both defined, the former takes precedence. (#221)
Description
The installation script ydbinstall.sh uses gtm* environment variables to control certain behavior:
gtm_buildtype
gtm_keep_obj
gtm_dryrun
gtm_group_restriction
gtm_gtm
gtm_lcase_utils
gtm_overwrite_existing
gtm_prompt_for_group
gtm_verbose
There should be ydb* equivalents for these environment variables (in addition to keeping the gtm equivalents for backwards compatibility). This makes the entire environment consistent using ydb* environment variables instead of relying upon the backwards compatibility.
Draft Release Note
The ydbinstall script used gtm* environment variables to control certain operations:
gtm_buildtype
gtm_keep_obj
gtm_dryrun
gtm_group_restriction
gtm_gtm
gtm_lcase_utils
gtm_overwrite_existing
gtm_prompt_for_group
gtm_verbose
These are replaced by ydb prefixed versions:
ydb_buildtype
ydb_keep_obj
ydb_dryrun
ydb_group_restriction
ydb_gtm
ydb_lcase_utils
ydb_overwrite_existing
ydb_prompt_for_group
ydb_verbose
The new environment variables are functionally equivalent to the old ones, just with a different prefix.
The text was updated successfully, but these errors were encountered:
The ydbinstall.sh script uses environment variables to control certain advanced
functionality of the script. These were previously gtm prefixed variables,
but for consistency purposes they should be ydb prefixed variables.
Modify the ydbinstall.sh script to look for ydb prefixed variables
and set the corresponding internal variable to the value of the ydb
prefixed variable, while mantaining backwards compatibility with gtm
prefixed variables.
The ydbinstall.sh script uses environment variables to control certain advanced
functionality of the script. These were previously gtm prefixed variables,
but for consistency purposes they should be ydb prefixed variables.
Modify the ydbinstall.sh script to look for ydb prefixed variables
and set the corresponding internal variable to the value of the ydb
prefixed variable, while mantaining backwards compatibility with gtm
prefixed variables.
ksbhaskar
changed the title
ydbinstall.sh uses gtm* environment variables
ydb_* environment variables to drive operation of ydbinstall.sh script
May 9, 2018
Final Release Note
The
ydbinstall.sh
script uses environment variablesydb_buildtype
,ydb_dryrun
,ydb_gtm
,ydb_group_restriction
,ydb_keep_obj
,ydb_lcase_utils
,ydb_overwrite_existing
,ydb_prompt_for_group
, andydb_verbose
to drive its operation, corresponding to the environment variablesgtm_buildtype
,gtm_dryrun
,gtm_gtm
,gtm_group_restriction
,gtm_keep_obj
,gtm_lcase_utils
,gtm_overwrite_existing
,gtm_prompt_for_group
, andgtm_verbose
. The latter remain supported, with the proviso that if aydb_
prefixed environment and the correspondinggtm_
prefixed environment variable are both defined, the former takes precedence. (#221)Description
The installation script
ydbinstall.sh
uses gtm* environment variables to control certain behavior:There should be ydb* equivalents for these environment variables (in addition to keeping the gtm equivalents for backwards compatibility). This makes the entire environment consistent using ydb* environment variables instead of relying upon the backwards compatibility.
Draft Release Note
The ydbinstall script used gtm* environment variables to control certain operations:
These are replaced by ydb prefixed versions:
The new environment variables are functionally equivalent to the old ones, just with a different prefix.
The text was updated successfully, but these errors were encountered: