v4.1.1

Gladly App Platform Enhancements and Changes

This release of appcfg introduces a more resilient CLI that captures diagnostics for debugging unexpected panics. It also simplifies the OAuth authorization flow for apps and enhances log recording defaults.

Breaking Changes

• OAuth flow
  The appcfg apps oauth command now launches your default browser to initiate the OAuth authorization_code flow. The -t/--token and -u/--user flags no longer apply to this command.
• Simplified detailed logging
  Running appcfg apps logs record-detailed without any flags now starts detailed logging by default for a 12-hour window; use --stop to end recording. (Previously you needed to supply --begin/--end, and sessions were limited to 6 hours.)

New Commands and Flags

• Add UI templates
  The appcfg add ui-template {template name} command scaffolds a full UI-template folder—config JSON, template, and test fixtures—for your GraphQL schema and type.

CLI Improvements

• Diagnostics on Panic: If appcfg crashes unexpectedly, it now generates an encrypted diagnostics file with helpful debugging context, including the error trace, CLI version, command path, OS, and architecture. This file can be shared with Gladly support.
• Completion-env generator
  appcfg apps completion-env helps you export the right environment variables for shell autocompletion.
• Extended logging window
  Detailed-logging sessions now default to 12 hours (up from 6 hours).

CLI Fixes

• Tweaked autocompletion to prevent invalid suggestions.
• Fixed line-wrapping inconsistencies in help text.
• -t/--token and -u/--user flags now only apply to commands that actually require credentials.