Conversation
…ng logic, and retrieving actionArgs from database CR
…mentsForType(typ)
…s is not allowed. This is important if operator is ran without webhoko validation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR contains the automation scaffolding for future db engine tests. The purpose of this PR is to limit the various code needed for the different db engines and have common functions handle the logic.
GetAppResponse() function for testing app connectivity for all tests
GetDatabaseResponse() for testing if database is successfully created
ProvisioningTestSetup and ProvisioningTestSetup helper method to be used for all tests
Setup methods and other common helpers used in various places such as creating type resources from YAMLS, creating logger, etc
I've attached images of the successful test runs.
pg-si_test.log