Mark
My feedback
-
257 votes
An error occurred while saving the comment Mark
supported this idea
·
-
36 votes
An error occurred while saving the comment Mark
commented
This completely breaks CICD and unexpectedly as the code is finished and we are implementing the CICD - this was not a welcome surprise. Hard to see a way to override this other than some hacky code to overwrite the deployment afterwards.
PLEASE don't add any more linked services without parameters for important values.
Mark
supported this idea
·
-
2 votesMark
shared this idea
·
-
24 votes
An error occurred while saving the comment Mark
commented
If this can protect from cyclical ownership, this would help us. It enables us to have an operations group who can all manage aspects of the group without having to give them a more powerful directory role. Oterwise, create a role action that purely enables group management (create/delete/update type operations) so we can assign that role a group for AD.
Mark
supported this idea
·
-
73 votes
An error occurred while saving the comment Mark
commented
SQL DWH scale rest API requires PATCH. We'd like to scale up before a pipeline run then scale back down afterwards. I have to work around this with an Azure function or a logic app which is more code to maintain. Would be much easier if you can simply support PATCH as an option.
-
7 votesMark
shared this idea
·
-
917 votes
An error occurred while saving the comment Mark
commented
I need this too for an IF activity. I get how a specific activity could do this but your "better still" comment, not sure how this would be implemented because there are 4 possible scenarios.
The activity generated and error and do we throw or not throw.
The activity generated no error and do we throw or not throw..My 2c would say have an activity whose only job is to create an error output (the red pill :-) ). This can be placed anywhere but especially useful in an IF activity on either the true or false branch.
-
6 votesMark
shared this idea
·
-
239 votes
This feature is planned in the upcoming months.
Mark
supported this idea
·
-
9 votesMark
shared this idea
·
Useful for testing. Current auto pausing means having to wait an hour between testing my retry logic and make sure no other devs hit the database. I could mock it but useful to have a real test for integration testing.
Any ideas when this capability may go into preview or release?