superfly/flyctl v0.0.452-pre-1

on GitHub

15ba1dc omitempty for apps v2
727ede0 Do not fail if headers are set for top level checks
5b87a7b simpler shorter interval
6ad66e2 Remove ignored GracePeriod and rename http checks
9475fe8 Revert changes to api.Check
e490210 remove debugging line
a06ce79 Ignore RestartLimit until we get backend support for it if ever
fdf2375 pass more field on toplevel checks
7394f27 Fix govet errors
6dd899b removed unused struct
4ccbc5a Reuse api.MachineCheck for service checks
b1ce19a Use references to process configs
6bda847 Respect check name
8f7dcf9 Interval can be nil
78fb208 fix merge conflict
11410a0 use lo.Assign to shallow copy processes map
7b2627d Create empty slices with expected capacity
bef83eb initalize empty list then append
3e38e3e do not override app.Config.Processes in GetProcessConfigs()
a0d467b fix panic in GetProcessConfigs()
1ad168a Fix check headers assignment
9d7a77f Do not convert service checks into toplevel checks
b98a693 add experimental to config
8fdb7bb use shlex instead of shellwords; it is already a dep
49987f6 fix bug with showing the statics prompt too often
61b3e7a use shellwords.Split() for processes too
3f1b621 use shellwords.Split() to get release_command in fly deploy
7055e4d add --override-cmd, --clear-cmd, --clear-auto-destroy flags to fly m clone
460e55e Fixes #1600. Provisions ips on first deploy
c70ba62 update fly deploy output for new machine to be consistent with updating machines
3bfdf91 Fix #1599: running fly deploy when app has not been deployed uses same logic as fly launch for picking the v1 vs. v2 platform
14e6f50 fly launch works for machines!
ee32655 use appConfig instead of definition in createRelease() mutation, plus pull in latest gql schema
e90f0ac fix app.Config tests
789772c fix validation for processes
c47a024 fly launch will use machines when able
ac70a83 fix bug in process validation
db25b06 WIP: start work on fly launch for apps v2
d1b35bf fix strategy set in app config, fix some processes related bugs, fix bug where env was getting copied from release_command to other machines
37c1424 auto destroy release_command, and skip dns for it
40ba7b5 add [metrics] support, fixed checks with processes, and got rid of volume names for machines
c54960b consider machines that are in "destroying" state inactive, and keep release_command machine after exit
5e2a8a4 processes support for fly deploy, destroy release_command machines, add --process-group flag to fly m clone
44db85b create machine on first deploy, fix bug where we built image twice for machines, and fix bugs with deployment after calling fly secrets set/unset
0fe4591 do not set checks on release_command machine.
75ca2ef get checks working plus add timeout flags
6c64026 clean up wait for state output
9b7e1b9 fix config metadata after #1571
7acd37a use iostreams.ColorScheme() instead of aurora to avoid metachars in terms that do not support them
ebd4c82 update default lease to be 10 minutes during deployment
ca493a1 fly deploy for machines: release_command
0858495 get rid of --skip-health-checks on fly deploy; use --detach in its place
973dc42 take 500ms to release leases even when context is canceled
2578b6c start of volume support for fly deploy for machines
7207900 fly deploy for machines support volumes
5345a87 print some logs while the deployment is running showing how it is progressing
4109f8e fly deploy for machines: wait for healthchecks before moving on, add --skip-health-checks flag to not
7270f20 address deepsource findings
a79eb90 fly deploy: concurrently acquire/release leases, update flaps.Wait() to better handle timeouts
71a529b fly deploy for machines for apps v2
3dfd157 fly launch shouldn't crash in empty directory