Reorganize the requirements files for Juniper tox tests #345
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.
The purpose of this commit is to clean up the requirements files. This makes things a bit clearer. We now have a "Juniper community" mode and a "Juniper multisite" mode.
juniper_community.txt
andjuniper_multisite.txt
requirements files read fromjuniper_base.txt
. Each of the 'community' and 'multisite' have only the package differences, which at this point is the version/branch ofedx-organizations
This PR is in preparation for another PR to improve asset building and testing devsite to support S3 based assets as well as local based assets