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.

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

[core 3.70 compat] Django storages config deprecation #2081

Closed
3 tasks done
pedro-psb opened this issue Jan 10, 2025 · 2 comments · Fixed by #2108
Closed
3 tasks done

[core 3.70 compat] Django storages config deprecation #2081

pedro-psb opened this issue Jan 10, 2025 · 2 comments · Fixed by #2108

Comments

@pedro-psb
Copy link
Member

pedro-psb commented Jan 10, 2025

Action for django's storages deprecation:

  1. Pre or on core-3.70 compat declaration:
    • Replace legacy with new
    • Settings on signal-handler
  2. On core 3.70 compat declaration: (closes this)
    • Use new setting in one CI scenario

See for context:
https://discourse.pulpproject.org/t/action-required-plugins-should-use-djangos-new-storage-config-for-3-70/1866

@netsandbox
Copy link

@mdellweg just a hint: pulp core 3.70.0 was released last week and the Docker image build fails because of the ansible plugin version constraint:

"pulpcore>=3.49.0,<3.70",

@mdellweg
Copy link
Member

Yep, I released it and that's expected for a so called "breaking change release". I fear pulp_ansible is just the first in line (alphabethically) to fail the builds. We are in the process of producing compatibility releases for all the plugins.

mdellweg added a commit to mdellweg/pulp_ansible that referenced this issue Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants