Allow for running Alfalfa integration tests on non-local deployment #517
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TShapinsky
force-pushed
the
nonlocal_test
branch
from
fb31313 to
bcd896a
Compare
TShapinsky
force-pushed
the
nonlocal_test
branch
from
68d450a to
10f5f1b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds
--host="<alflalfa_host>"option to pytest.This allows for Alfalfa integration and API tests to be run on a remote instance. This is useful for validating a new deployment. After running these tests on on lab instances I discovered a small bug in the Alfalfa deployment helm chart which will be addressed in the next couple days.