Bump deprecation warning to Aluminium for neutron module #55664
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
the neutron module was set to be deprecated in
neon
in favor of neutronng but if you look at all the uses ofsalt.utils.openstack.neutron
which the neutron module uses when initializing its auth there is the neutron pillar that is still using the old nuetron module. So I added this issue: #55663 to track the work to migrate the neutron pillar to use the new neutronng module instead before we can entirely deprecate theneutron
module. So for now we are going to bump the deprecation warning in the neutron module to gives us enough time for this migration.This PR also fixes an issue where the
salt.utils.openstack.neutron
tries to call__utils__
to add the deprecation warning, but__utils__
is not packed into the utils loader so it fails.What issues does this PR fix or reference?
#49430