Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: Removal of top-level --file breaking change #5308

Merged
merged 2 commits into from
May 23, 2024
Merged

docs: Removal of top-level --file breaking change #5308

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ae64bdd
docs: Removal of top-level --file breaking change
TheRealFalcon May 20, 2024
b2983fc
apply suggestion
TheRealFalcon May 23, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions doc/rtd/reference/breaking_changes.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,25 @@ releases.
many operating system vendors patch out breaking changes in
cloud-init to ensure consistent behavior on their platform.

24.1 - Removal of ``--file`` top-level option
=============================================

The ``--file`` top-level option has been removed from cloud-init. It only
applied to a handful of subcommands so it did not make sense as a top-level
option. Instead, ``--file`` may be passed to a subcommand that supports it.
For example, the following command will no longer work:

.. code-block:: bash

cloud-init --file=userdata.yaml modules --mode config

Instead, use:

.. code-block:: bash

cloud-init modules --file=userdata.yaml --mode config


23.2-24.1 - Datasource identification
=====================================

Expand Down
Loading