Skip to content

Conversation

@rishichawda
Copy link
Member

Description

backport of #1873

Related Issue

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

  • I have read the CONTRIBUTING document.
  • I have run the pre-merge tests locally and they pass.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • If Gemfile.lock has changed, I have used --conservative to do it and included the full output in the Description above.
  • All new and existing tests passed.
  • All commits have been signed-off for the Developer Certificate of Origin.

In 2015, I wrote a new filesystem plugin (#559), because the original
one used non-unique keys and so the data was not only incomplete but
inconsistent. Since it was backwards incompatible, we called it
`filesystem2`, and agreed to a migration path.

That original PR only implemented it for linux, however, and it shortly
followed with #564 for Darwin/OSX.

The plan was, at that time to keep both for one major version (give
people the chance to migrate to fs2), then for one major version make
both names (`filesystem` and `filesystem2`) so that people could move
back to the name `filesystem`, and then we'd finally drop the
`filesystem2` name.

Unfortunately, other platforms never got FS2 support, so this got hairy.

In 2018 I wrote #181 which unified the various platforms' plugins so it
was easier to implement fs2 on more platforms. Shortly there after I
wrote #1266 that implemented fs2 for the rest of the unixes. And
finally, I wrote #1267 implemented Windows to filesystem2.

This was all still before Chef 17. For Chef 17 I wrote #1662 which
finally made windows have the new data in the original name, the
second-to-last-step. The plan being that in 18 we'd finally remove
the `filesystem2` name... but we forgot to do that.

This, is the final bit - remove all references to filesystem2.

Closes #1872

Signed-off-by: Phil Dibowitz <phil@ipom.com>
@rishichawda rishichawda requested review from a team and jaymzh as code owners December 18, 2025 11:45
@rishichawda rishichawda changed the title The filesystem plugin transition is finally over (#1873) [18-stable:backport] The filesystem plugin transition is finally over (#1873) Dec 18, 2025
@rishichawda rishichawda changed the title [18-stable:backport] The filesystem plugin transition is finally over (#1873) [18-stable:backport] filesystem plugin transition Dec 18, 2025
@sonarqubecloud
Copy link

@sonarqube-for-infrastructure-prod

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@johnmccrae johnmccrae merged commit 9ceb65e into 18-stable Dec 18, 2025
45 of 46 checks passed
@johnmccrae johnmccrae deleted the rishichawda/backports/jaymzh/kill-fs2 branch December 18, 2025 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants