Releases: section/sectionctl
v1.9.1
v1.9.0
This release includes small usability improvements and bugfixes:
- Update: Add watch support to
sectionctl ps#94 - Update: Add short flag for
deploysubcommand #95 - Update: Suggest next steps when the app creation fails #97
- Update: Write debug logs to a file, to make it easier to report problems #99
- Update: Add a
stackssubcommand to see what stacks new apps can be created with #100 - Update: Suggest next steps when
sectionctl loginfails #103 - Bugfix: Make
sectionctl apps initmore robust #101 - Bugfix: Hide the
Section-Tokenheader value in debug output, so credentials aren't leaked #96
v1.8.0
v1.7.0
This release adds two new subcommands (sectionctl domains and sectionctl apps init) and extends the behavior of an existing subcommand (sectionctl version).
Highlights from this release include:
- Feature: Add
sectionctl apps initsubcommand, for bootstrapping a Node.js application for deployment on Section (#89) - Feature: Add
sectionctl domainssubcommand, to list domains on an account (#87) - Feature: Add a version checker that prompts you to upgrade (#85)
- Update: Increase the default timeout value, so
sectionctl deployworks more reliably with larger apps (#84) - Update: Order subcommands alphabetically, to make them more readable (#88)
v1.6.1
v1.6.0
This release is mostly bugfixes and small usability updates.
Highlights from this release:
- Feature: Add a
--followflag tologssubcommand to tail the log (#76) - Update: Add short flag (
-n) for specifying the number of log lines to return (#79) - Update: Add ability to skip client side validation on Node.js workload deploys (#75)
- Update: Remove analytics, as they were causing problems in CI/CD environments (#74)
- Update: Increase timeouts across the board, and make them configurable with
--section-api-timeout(#73) - Update: Surface rate limits when reached (#77, #79, #81)
v1.5.0
This release adds the sectionctl logs subcommand, for viewing application and access logs. This helps you understand how your Node.js applications are behaving on Section's edge compute platform.
Highlights from this release:
- Feature: Add a
sectionctl logssubcommand for viewing application and access logs (#64, #65, #66) - Feature: Add ability to create and delete applications via
sectionctl apps createandsection apps delete(#68) - Update: Support supplying a token on the command line when logging in (#67)
- Bugfix: Don't require user to be logged in to run
sectionctl version(#69)
v1.4.0
This release allows the Node.js application to be deployed into non-default directories inside Section Git repository. It also fixes a bug that stopped sectionctl from working when API tokens are specified as environment variables.
Highlights from this release:
- Feature: Add optional
--app-pathflag tosectionctl psandsectionctl deploysubcommand to specify the folder name in Section Git repository (#61) - Update: Add spinners to
accounts,apps,ps,whoamisubcommands (#58) - Update: If analytics are enabled, make sectionctl run a lot faster (#57)
- Update: Add missing helper text for
pssubcommand flags (#56) - Bugfix: Make tokens work when there are no stored credentials (#62)
- Bugfix: Windows binaries in the release tarball now have the correct
.exefile extension - Bugfix: Raise auth specific errors (#63)
- Bugfix: Ensure short flags are unique (#55)
v1.3.0
This release simplifies how you authenticate sectionctl: you can now authenticate with a personal access token issued through the Section console.
Highlights from this release:
- Feature: Add
sectionctl pssubcommand to see application status (#51) - Feature: Add ability to set credentials via environment variables (#43)
- Update: Switch to tokens for authentication (#53)
- Update: Make deploy environment configurable when deploying an app (#46)
- Update: Make log levels more tunable (#47 )
v1.2.0
Highlights from this release:
- Feature: Add bash completion on subcommands and flags (#40)
- Update: Add flag to not delete temporary upload tarball (#41)
- Update: Output the transaction ID on error, so users have something to provide to Section support when lodging a support ticket (#38)
- Update: Add a check for presence of
server.confwhen deploying Node.js apps, so deploys don't fail in unexplained and unobvious ways (#39) - Bugfix: Make the
--account-idand--application-iddeploy flags required, and set no defaults for either of them (#37)