-
Notifications
You must be signed in to change notification settings - Fork 57
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
ServerName should not be needed #38
Labels
Comments
kanika1894
added
enhancement
New feature or request
and removed
need-to-triage
Requires investigation
labels
Jun 2, 2021
This issue is idle because it has been open for 14 days with no activity. |
This issue is idle because it has been open for 14 days with no activity. |
dzsquared
added a commit
that referenced
this issue
Jan 5, 2022
* proposed improvement #38 * Update main.ts fixed null/empty check * moved check for required server address * added more connection string tests * improved code readability * updated readme * updated action.yml * updated readme * re-added support to server-name to retain backward compatibility * removed unused code? * improved readme * corrected typos * use server-name if specified * added debug message and comment * resolving test failure for connectionString.server Co-authored-by: Davide Mauri <damauri@microsoft.com>
Now available in v1.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given that the connection string already contains the server name, the property ServerName in the YAML file should be removed. Just like the database name is retrieved from the connection string, also the server name can be retrieved from the connection string, therefore asking one param less to the end user
The text was updated successfully, but these errors were encountered: