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

bring back CRS 2.x to 3.x renumbering utility #1278

Merged
merged 2 commits into from Jan 4, 2019

Conversation

Projects
None yet
3 participants
@lifeforms
Copy link
Collaborator

lifeforms commented Jan 4, 2019

Turns out that I actually still stumble upon some customer CRS 2.x installs in production.

This makes the CRS 2.x to CRS 3.x migration utility useful again. I had to grab it from the v3.0 tree, but also made some slight improvements to text, code style and Python3 compatibility.

@lifeforms lifeforms added this to the CRS v3.2.0 milestone Jan 4, 2019

@csanders-git

This comment has been minimized.

Copy link
Collaborator

csanders-git commented Jan 4, 2019

Interesting, thanks

@dune73

This comment has been minimized.

Copy link
Collaborator

dune73 commented Jan 4, 2019

Ah, the removal went so smooth. But I agree it makes sense to bring back an improved version if you still encounter CRS2 it in PROD.

@lifeforms lifeforms merged commit 6cd4aa1 into SpiderLabs:v3.2/dev Jan 4, 2019

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment