feat(client-only-schemas): remove schemas for EOL Juju 3.2 #1113
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.
Remove
3.2.X
schemas. Delete_client*.py
and runmake client
.Description
Moving towards the goal of having schemas and generated code in python-libjuju only for the latest supported Juju versions (
3.1.9
,3.3.6
,3.5.4
,3.5.3
), and using client only schemas (see #1099), this PR removes schemas for EOL Juju 3.2, and reruns code generations, removing_client*.py
files and then runningmake client
.QA Steps
CI steps should all continue to pass, except for integration testing which should continue to fail with the usual suspects (see #1108 for a non-exhaustive table of tests that sometimes fail on
main
).Notes
To hopefully simplify the diffs, this is the first PR in a planned sequence of PRs that will depend on each other. Subsequent PRs will be:
3.1.9
,3.3.6
) and regenerate code3.4.5
and regenerate code3.5.3
and regenerate code