-
Notifications
You must be signed in to change notification settings - Fork 24
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
Automation mssql #141
base: main
Are you sure you want to change the base?
Automation mssql #141
Conversation
…g, and createSetupConfig
Merging with main
…ration to 'provisioning' file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor comments and a question:
Why do we have 2 pg - si tests? Can we combine those into one?
Also, what do you think about moving the files appConnectivity.go
, provisioning.go
and setup.go
into a commons folder?
automation/provisioning.go
Outdated
|
||
// Nil check | ||
if st == nil || clientset == nil || v1alpha1ClientSet == nil { | ||
errMsg := "Error: ProvisioningTestSetup() starting ended! " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use a better statement here instead of starting ended
?
Perhaps something like nil parameters/arguments
or initialization failed
etc?
…paths, and added slight logs
What this PR does / why we need it:
How Has This Been Tested?:
-- app connectivity for MSSQL failing. This is not a code issue, rather a pod/image issue. I'm investigating this now.
pg-si_test.log
mssql_test.log