Skip to content

Commit

Permalink
Remove feature flag override ability (#4228)
Browse files Browse the repository at this point in the history
It has gone unused since its introduction, could possibly be
misinterpreted as a user-facing feature, and complicates testing.
  • Loading branch information
TheRealFalcon authored Jul 6, 2023
1 parent 317a023 commit e2a7178
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 84 deletions.
13 changes: 2 additions & 11 deletions cloudinit/features.py
Original file line number Diff line number Diff line change
Expand Up @@ -5,11 +5,8 @@
downstream configuration changes.
Currently used upstream values for feature flags are set in
``cloudinit/features.py``. Overrides to these values (typically via quilt
patch) can be placed
in a file called ``feature_overrides.py`` in the same directory. Any value
set in ``feature_overrides.py`` will override the original value set
in ``features.py``.
``cloudinit/features.py``. Overrides to these values should be
patched directly (e.g., via quilt patch) by downstreams.
Each flag should include a short comment regarding the reason for
the flag and intended lifetime.
Expand Down Expand Up @@ -79,9 +76,3 @@
(This flag can be removed when Jammy is no longer supported.)
"""

try:
# pylint: disable=wildcard-import
from cloudinit.feature_overrides import * # noqa
except ImportError:
pass
73 changes: 0 additions & 73 deletions tests/unittests/test_features.py

This file was deleted.

0 comments on commit e2a7178

Please sign in to comment.