Yo

Latest version: v1.6.0

Safety actively analyzes 627310 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 3

1.6.0

New Features:

- The `yo list` command now has a completely configurable table.
- Columns may be specified as a list in the config file (`list_columns`)
- An alternative list may be specified via `yo list -C a,b,c`
- Columns can be added to the end of the table with `yo list -x Column`
- The `yo list` command includes a new column, `ResourceType`, which corresponds
to the value of the `Oracle-Recommended-Tags.ResourceType` tag.

1.5.1

Another tiny release, which I configure a "bugfix release".

Fixes:

- Fixed a crash with `yo nmi`
- Added `--ad` option to `yo launch` which was a bit of an oversight

1.5.0

This is a very tiny release with just three changes.

New Features:

- The "yo attach" and "yo detach" commands now work with boot volumes.

Fixes:

- Allow "yo teardown" operation to occur in states other than RUNNING.
Specifically, it should be possible to teardown STOPPED instances. The
operation isn't permitted in TERMINATED or TERMINATING states.
- Respect the termination protection option for "yo teardown". Previously, "yo
teardown" would happily terminate a protected instance.

1.4.0

This version of Yo comes with some major improvements.

New Features:

- Two new instance actions are added: "teardown" and "rebuild". The teardown
operation terminates the instance, but preserves the boot volume, and attaches
some metadata to the instance so that Yo will know how to rebuild it the way
it was. The "rebuild" operation does exactly that.
- This operation might be preferred instead of "stop" and "start" in cases
where your tenancy is encountering service limits. Stopped instances still
count toward your service limits, while terminated instances do not.
- Please note that for now, "teardown" cannot remember what block volumes were
attached to your instance, and so "rebuild" will not reattach block volumes
(aside from the boot volume, of course). This feature could be added if
there is demand for it.
- You may now specify a custom username for your instances! This can be
specified in your instance profile configuration, or on the `yo launch`
command line. Yo will automatically keep track of the username for each
instance using a tag, so you don't need to remember which you chose. So the
existing `yo ssh` commands will work regardless of your username choice.
- You may now specify a boot volume to launch an instance from. If you
terminated a volume with (`--preserve-root`), then you can launch an instance
from the same boot volume. This operation is similar to "rebuild", except that
you must manually specify the instance shape, name, etc.
- There is a new command, `yo copy-id`, which wraps `ssh-copy-id`. Use it to
copy SSH keys over to an instance. For the most part, you shouldn't need this
because Yo passes your key in anyway, but it could be useful to add more keys.

Changes:

- The default configuration of Yo now specifies the `VM.Standard.x86.Generic`
shape with 1 CPU and 8 GiB of memory.
- The `yo list` command no longer shows instances in `TERMINATING` state.
- The `yo -h` help output is now organized into logical categories with
well-written command summaries.
- Documentation for each Yo sub-command is now automatically generated to match
the CLI.
- Sub-commands are now permitted: commands like `yo volume-list` are now `yo
volume list`. However, the old spellings are still permitted, as we don't want
to break anybody's muscle memory.
- Yo's command aliasing is now improved. Prior to this release, Yo used
shortest-prefix aliasing, but if you wanted to specify your own alias mapping,
then shortest-prefix mappings were disabled. This limitation has now been
removed. If you specify custom aliases, then Yo will use them, and will still
create shortest-prefix aliases for the rest of the commands.

Fixes:

- Fixes an error due to a missing minimum version of the `rich` library.
- If you have provided memory / cpu configurations in an instance profile, but
you then override the profile with a non-flex shape, Yo used to raise an
error. However, this isn't a very helpful error: it's clear the user wants the
non-flex shape and forgot about the default flex configuration. So we've
removed this unnecessary error.

1.3.1

Fixes:

- Fix `FileExistsError` on Windows.

1.3.0

Changes:

- The look & feel of Yo has been updated a bit. Progress bars have been removed
in favor of spinners, since we can't accurately predict progress most of the
time anyway. The spinners also show the time elapsed even after completion, so
that you know how long Yo spent waiting for each action. Most of the printouts
now also include a timestamp.
- Yo now catches Ctrl-C gracefully and exits without a traceback.
- The `creator_tags` configuration option is added. This configuration is
related to how Yo tracks instances which you've created. If Yo is already
working for you, there's no need to care about it.

Fixes:

- Fixed some bugs related to parsing information in InstanceProfile.
- Fixed a very rare bug related to the automatic update checking.
- Fixed a bug related to the default configuration of memory for flexible CPU
instances.

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.