Skip to content

Conversation

@glomaga
Copy link

@glomaga glomaga commented Jan 7, 2019

To be able to use the task in a SQL Server environment without Azure, an additional parameter was added to control which type of execution you want to perform.

Added logic to check SQL module availability (SqlServer or SQLPS, depending on the version of PowerShell) to speed up execution where this is already available.

Gloria Gallego added 2 commits January 7, 2019 10:17
… an additional parameter was added to control which type of execution you want to perform.

Added logic to check SQL module availability (SqlServer or SQLPS, depending on the version of PowerShell) to speed up execution where this is already available.
@riserrad
Copy link
Owner

riserrad commented Mar 9, 2019

Hi @glomaga ! Thank you so much for your contribution and sorry for the delay. For some reason, GitHub did not notified me about your PR.

I'll make sure to review and test your changes and go forward with your PR.

Cheers

[string]$openCoverXmlFile,
[string]$coberturaFileName,
[string]$htmlReportsOutput,
[string]$queryTimeout
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There may have a comma missing here, after $queryTimeout.

I think it breaks the code execution. But in case we're not sure, it would be good to keep the standard.

"name": "enableAzure",
"type": "boolean",
"label": "Enable Azure SQL",
"defaultValue": "false",
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As we've been working on a cloud world, do you think that it makes sense to leave it true by default?

"label": "Enable Azure SQL",
"defaultValue": "false",
"required": false,
"helpMarkDown": "If you want to get the result from a Azure SQL Server, enable this.",
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was also thinking about requesting this info from the user as a Dropdown list. What do you think?

This way, we could ask for something like:

"SQL Server technology/service type":

  • SQL Server On Premises
  • Azure SQL

And then we'd handle this on the scripts.

Copy link
Owner

@riserrad riserrad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Such a great idea to support both SQL onprem and Azure SQL by adding some fine tune to it. I loved it.

I left some comments that I'd love to hear from you what you think.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants