-
Notifications
You must be signed in to change notification settings - Fork 218
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
launch
: Use appconfig.Compute for Plan guest information. (#3219)
Moves us towards supporting multiple compute sections in a launch plan. This means, among other things, that we'll support round-tripping a full guest config, with fields such as GPU support or host dedication IDs. Also fixes a couple bugs and outstanding weirdnesses with fly.toml import launches. Squashlog: * `launch`: use Compute instead of MachineGuest This moves us closer to how fly.tomls get serialized Unfortunately, we'll have to do some weird plan patching in a later commit to make this compatible with the plan shape the UI currently expects * `deploy`: remove optionalGuest param, now that it's unused * `launch`: polyfill `Plan.Compute` now with existing guest fields This means we can write code *now* that expects the Launch Plan to have full compute fields, but also means that when the UI gets support for returning them, then we'll automatically start supporting that. * `Flatten()`: move compute determination to own func This allows launch to piggyback off the same logic. Initially I wanted to just copy-paste this into Launch and be done with it, but I had to copy `matchesGroups` too which just turns it into a big mess of unmaintainable code. Not that this is *much* better, but it's a little better (I hope) * `launch`: replace compute determination with `ComputeForGroup()` * `fly_launch_test`: memory_mb: 1024 -> memory: "1gb" * `launch`: maintain guest options that can't be set from web UI
- Loading branch information
Showing
8 changed files
with
199 additions
and
81 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.