For `fuelup` and each of its subcommands: - Create an InfluxDB schema - Import the schema to our online InfluxDB bucket - Add the code to capture metrics - Create tests `fuelup` and its subcommands: - fuelup - exit-status - run-time - fuelup-check - exit-status - run-time - fuelup-completions - exit-status - run-time - shell - fuelup-component - exit-status - run-time - fuelup-component-add - exit-status - run-time - forc - forc@ - fuel-core fuel-core@ - fuelup-component-remove - exit-status - run-time - forc - fuel-core - fuelup-component-list - exit-status - run-time - fuelup-default - exit-status - run-time - toolchain - fuelup-self - exit-status - run-time - fuelup-self-update - exit-status - run-time - force - fuelup-self-uninstall - exit-status - run-time - force - fuelup-toolchain - exit-status - run-time - fuelup-toolchain-install - exit-status - run-time - name - latest - nightly - testnet - mainnet - fuelup-toolchain-new - exit-status - run-time - fuelup-toolchain-uninstall - exit-status - run-time - fuelup-show - exit-status - run-time - fuelup-update - exit-status - run-time - fuelup-upgrade - exit-status - run-time - force
For
fuelupand each of its subcommands:fuelupand its subcommands:fuelup
fuelup-check
fuelup-completions
fuelup-component
fuelup-component-add
fuel-core@
fuelup-component-remove
fuelup-component-list
fuelup-default
fuelup-self
fuelup-self-update
fuelup-self-uninstall
fuelup-toolchain
fuelup-toolchain-install
fuelup-toolchain-new
fuelup-toolchain-uninstall
fuelup-show
fuelup-update
fuelup-upgrade