Skip to content

Conversation

pedro-psb
Copy link
Member

Summary of how the storage setting are rendered:

  • pulpcore <3.70 support only legacy storage
    • test_storages_compat_layer must be unset
    • only legacy settings are rendered
  • pulpcore >=3.70,<3.85 supports both legacy and new storage
    • test_storages_compat_layer must be True
    • both types of settings are rendered (for testing)
  • pulpcore >=3.85 support only new storage
    • test_storages_compat_layer must be False
    • only new settings are rendered

@pedro-psb pedro-psb force-pushed the 6838-remove-storages-ci branch from 766a778 to 2821337 Compare August 7, 2025 21:28
@pedro-psb pedro-psb changed the title Modify settings.py.j2 storages to work with older and newer branches [PULP-659] Modify settings.py.j2 storages to work with older and newer branches Aug 7, 2025
@pedro-psb pedro-psb force-pushed the 6838-remove-storages-ci branch 2 times, most recently from 9357ad6 to 35c420f Compare August 7, 2025 22:00
@pedro-psb pedro-psb marked this pull request as draft August 7, 2025 23:41
@pedro-psb
Copy link
Member Author

Need to fix pulp/pulpcore#6838 first

Summary of how the storage setting are rendered:

- pulpcore <3.70 support only legacy storage
  * test_storages_compat_layer must be unset
  * only legacy settings are rendered
- pulpcore >=3.70,<3.85 supports both legacy and new storage
  * test_storages_compat_layer must be True
  * both types of settings are rendered (for testing)
- pulpcore >=3.85 support only new storage
  * test_storages_compat_layer must be False
  * only new settings are rendered
@pedro-psb pedro-psb force-pushed the 6838-remove-storages-ci branch from 35c420f to 7ebcd70 Compare August 11, 2025 12:07
@pedro-psb pedro-psb marked this pull request as ready for review August 11, 2025 14:49
@pedro-psb pedro-psb merged commit 428aa9d into pulp:main Aug 11, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants