Proposal: v2 of sql-action about sql-action HOT 9 CLOSED

Following on what @dzsquared proposed, maybe we can just use the word input-type instead of file-type so that it can be a bit more open to what it accepts as values, and then we can use sql-command as an option to indicate that the SQL query is provided right in the yaml file, in a new dedicated property, for example: command.

 input-type:
    description: 'The input type. Options: sql-file, project-file, dacpac, sql-command'
    required: true
 sql-command:
    description: 'In case input type is sql-command, the sql command that will be executed'
    required: false

from sql-action.

As work as been underway on v2, the proposed interface is revised to simplify and allow the potential for extension to additional sqlpackage commands.

• The action parameter has become required and the file-type parameter is removed from the proposal.
• The arguments option is specified as sqlpackage-arguments

(this is being updated in the post above as well)

from sql-action.

This issue is idle because it has been open for 14 days with no activity.

from sql-action.

I’ve been involved in some discussions where its come up that it would be really helpful to run some queries/TSQL commands that are generated during the pipeline without going through the step of writing it to file. This is part of what we’ve taken away from being able to pass sqlcmd variables in, although even that wasn’t especially intuitive.
Could the addition of a file-type value along the lines of sql-query (or interactive-query, sql-command, run-command) be helpful for your use cases?

from sql-action.

This issue is idle because it has been open for 14 days with no activity.

from sql-action.

This issue is idle because it has been open for 14 days with no activity.

from sql-action.

As work as been underway on v2, the proposed interface is revised to simplify and allow the potential for extension to additional sqlpackage commands.

• The action parameter has become required and the file-type parameter is removed from the proposal.
• The arguments option is specified as sqlpackage-arguments

(this is being updated in the post above as well)

After further discussion and user feedback, we have replaced the script action with go-sqlcmd in #113. We are keeping the arguments input from v1 to be for additional sqlpackage arguments when Publishing to database, and be for additional sqlcmd arguments when Script action is used. This has been updated in the description above.

There are some breaking changes from the go-sqlcmd arguments that may require changes to your yaml files still: https://docs.microsoft.com/en-us/sql/tools/go-sqlcmd-utility?view=sql-server-ver16#breaking-changes-from-sqlcmd

from sql-action.

Work for v2 is nearing completion and is available for testing through https://github.com/azure/sql-action/tree/v2

Prior to release at https://github.com/Azure/sql-action/releases the v2 work can be used for evaluation and we appreciate you reporting any issues you find.

There are a few items to finish up in the v2 milestone and we anticipate the release will be ready in September.

from sql-action.

This issue is idle because it has been open for 14 days with no activity.

from sql-action.