There’s a new flyctl (v0.0.137) available for your command line, with cleaner commands and extra helpers. Find out more about it in the Changelog.
This flyctl release brings in some big changes in the command structure as we move to an app-centric command style. What does that mean? Well, the
apps subcommand is being deprecated; we’ve kept it in place for this release but now all its commands have top level commands of their own:
|apps list||list apps|
suspend commands also now take an appname as their last argument. The status command has also followed suit in this change, so you can now type
flyctl status appname rather than
flyctl status -a appname - The
-a option will remain supported.
The list command at the top level has been around for a while and has advantages over the older list command: you can match appnames with fragments of text and filter on status or organization. Talking about organizations,
flyctl list orgs will list the organizations your account has access to.
We’ve also made some small usability changes in how you initialize an application. The
init command offers you a selection of builders or the chance to use a Dockerfile. If you don’t have one,
init will create one for you with a simple hello world deployment to get you going. If you don’t want the example generated, use
--dockerfile when running
init. And, yes, you can still specify a builder with
--builder, that’s not going away.
movecommand will now tell you what organization your app is in so you know where you are moving it from.
- Setting and unsetting
secretson suspended deployments is now blocked.
- Setting and unsetting
secretswill start a deployment monitor. Add the
--detachflag to return before starting the deployment monitor.
- If you are setting a secret on an undeployed app, then we don’t start the deployment monitor, so no need to –detach.
infocommand now supports
--hostwhich will display just the host name, along with (
--name) which just displays the appname. These flags are designed to make it easier to script with flyctl.
versioncommand now outputs just the bare version number - add
--fullto get the detailed version/commit/date information if you need it.
It’s not all been flyctl changes. There’s a fix for a problem with cookie headers and HTTP/2 which is now in place. Also, if your application parses headers, you’ll find that a Via header has been added to enable applications to trace their route through the Fly edge.
This is the Fly Changelog where we list all significant changes to the Fly platform, tooling and web sites. You can also use the RSS feed of just changelog posts available on fly.io/changelog.xml or consult our dedicated ChangeLog page with all the recent updates.
flyctl: Version 0.0.137 released
- New top level commands
- Apps subcommand deprecated
--hostadded to info command
versiondisplays bare version number,
--fulldisplays full details
secretssetting and unsetting will follow deployment where appropriate
movecommand now prompts with current organization
initcommand now prompts with list of builders or option to create/use Dockerfile
--dockerfileflag to completely skip builder query
- Fixed a bug related to incoming HTTP/2 request cookies sent as multiple headers. Incoming HTTP/2 connections can present multiple cookie headers. The headers were sent on as is when the Fly edge downcast the connection to HTTP/1 which is used within the Fly network. Some servers could not handle the multiple headers though. Now, the downcasting process concatenates the multiple cookie headers into a single cookie header.
- Added the Via header to both http requests and responses
- Boosted the performance of the
Optimizing Imagephase of deployment by making better use of existing identical images.