Problem
tabcmd 2's editsite command is missing many flags that tabcmd Classic supports. Scripts using any of these will silently do nothing or error when run against tabcmd 2:
| Flag |
Description |
--metrics-level / -m |
|
--guest-access-enabled / -g |
|
--cache-warmup / --no-cache-warmup |
|
--cache-warmup-threshold |
|
--subscription-email / -e |
|
--subscription-footer / -f |
|
--web-extraction-enabled |
|
--allow-subscriptions / --no-allow-subscriptions |
|
--allow-web-authoring / --no-allow-web-authoring |
|
--allow-mobile-snapshots / --no-allow-mobile-snapshots |
|
--time-zone |
|
--use-default-time-zone |
|
The REST API endpoints to support all of these exist. This is a gap in the CLI surface only.
Expected behavior
editsite should accept all of the above flags to match Classic behavior and allow existing scripts to work unchanged.
Problem
tabcmd 2's
editsitecommand is missing many flags that tabcmd Classic supports. Scripts using any of these will silently do nothing or error when run against tabcmd 2:--metrics-level/-m--guest-access-enabled/-g--cache-warmup/--no-cache-warmup--cache-warmup-threshold--subscription-email/-e--subscription-footer/-f--web-extraction-enabled--allow-subscriptions/--no-allow-subscriptions--allow-web-authoring/--no-allow-web-authoring--allow-mobile-snapshots/--no-allow-mobile-snapshots--time-zone--use-default-time-zoneThe REST API endpoints to support all of these exist. This is a gap in the CLI surface only.
Expected behavior
editsiteshould accept all of the above flags to match Classic behavior and allow existing scripts to work unchanged.