-
Notifications
You must be signed in to change notification settings - Fork 58
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
Feature request: Decouple using managed identity from updating sql network settings #186
Comments
This is definitely unexpected. Any changes to Azure resource state should be explicitly opt-in rather than implicit as a result of some earlier run action. |
This issue is idle because it has been open for 14 days with no activity. |
bump. |
This issue is idle because it has been open for 14 days with no activity. |
The action attempts to add a firewall rule if it cannot login to the SQL instance. It first tries the master db, then the user db from the connection string. You may get more insights to the initial login failures with debug logging enabled: https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging |
This issue is idle because it has been open for 14 days with no activity. |
It appears this is not functioning correctly though - in my build I can successfully deploy the database (as a managed identity) but I still get the warning about the firewall. I'd like to be able to opt out of the firewall behaviour altogether (per #205 (comment)) - I don't like that the action silently attempts to change a security-sensitive azure config with no way to opt out |
This issue is idle because it has been open for 14 days with no activity. |
I am trying to apply migrations from a self hosted runner. The runner has network access to the sql server via private endpoint and does not need any new network openings. The SQL server denies public access.
It seems as the
sql-action
is hard coded to attempt adding network rules if azure/login is foundI end up with a
I would like there to be an input var to skip this step entirely, as I have no interest in ad-hoc openings towards the sql server.
I also tried not granting the managed identity access to any subscriptions, setting this
this however failed with this error:
The text was updated successfully, but these errors were encountered: