Skip to content
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

Azure SQL Publish not supported on Linux build agent #15194

Open
k290 opened this issue Aug 24, 2021 · 14 comments
Open

Azure SQL Publish not supported on Linux build agent #15194

k290 opened this issue Aug 24, 2021 · 14 comments

Comments

@k290
Copy link

k290 commented Aug 24, 2021

There is no way to execute SQL scripts generated from EF Core from a Linux agent without workarounds that would require:

  1. Access to the agent to install a SQL Agent
  2. Implementing complicated containers

This was originally raised here: #8408 but was closed in 2018 as "it had been added to the backlog".

The issue should remain open until the feature/fix is in place.

@github-actions
Copy link

github-actions bot commented Mar 6, 2022

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

@github-actions github-actions bot added the stale label Mar 6, 2022
@k290
Copy link
Author

k290 commented Mar 6, 2022

Commenting as still relevant to avoid going stale.
Also worth linking the corresponding item on developer community that has gathered some votes: https://developercommunity.visualstudio.com/t/Allow-Azure-SQL-Publish-SqlAzureDacpacD/1453203

Please cast your vote if you think it would be worthwhile for this to be supported on linux

@github-actions github-actions bot removed the stale label Mar 6, 2022
@hunyhabib
Copy link

Commenting as still relevant to avoid going stale, i feel this is important feature as all our agents are linux and it should be supported by the task out of the box without workarounds.

@DaleyKD
Copy link

DaleyKD commented Sep 13, 2022

Trying to keep this alive. Seems silly to have to use a Windows agent for this.

@SteveBurkettNZ
Copy link

Just stumbled across limitation when our SQL guys wanted to start using the build hosts for the environment. Going to have to create a Windows build host for them as a work around. Darn.

@preethamrajk
Copy link

Hi @vijayma

Is there an update to this issue/feature-request? This is affecting us in production.

@preethamrajk
Copy link

Also, a dumb question!

Will this task work if Powershell and the InvokeSqlCmd modules are installed on Linux agents?

@pawel-zolty
Copy link

I also wait for this feature :)

@eastjie
Copy link

eastjie commented May 30, 2023

I also wait for the feature. Thanks very much :)

Copy link

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

@github-actions github-actions bot added the stale label Nov 26, 2023
@DaleyKD
Copy link

DaleyKD commented Nov 26, 2023

Don't let this go stale, please.

@github-actions github-actions bot removed the stale label Nov 26, 2023
@vanmash
Copy link

vanmash commented Feb 28, 2024

Microsoft loves Linux, really?

Please support this task on Linux

@rayou18
Copy link

rayou18 commented Apr 26, 2024

A work around if you have "Access to the agent" and the agent is running linux:
#8408 (comment)

@k290
Copy link
Author

k290 commented Apr 26, 2024

A work around if you have "Access to the agent" and the agent is running linux: #8408 (comment)

Its an alternative tool to get the job done, and as you point out, no good if you're using a Microsoft agent. SQL migrations of course work differently to dacpacs. Its better than dacpacs in some use-cases and worse in others.

As an aside we started trying to do a release with entity framework migrations.
We did switch to EF SQL migrations invoked like this, but as time went on, we found they were brittle and limited in what they could do, due to how you need to generate the EF migrations into a large SQL file. They get nested in IF statements in a single large SQL file. You end up with transaction issues, and can put things in a state that makes it difficult to roll back if something failed.

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

No branches or pull requests