for linked service property:
when having a string in workspace (screenshot 1) , and in git (branch) it is still a string (screenshot 2), it gets deployed as an int in the deployed workspace (screenshot 3).
i have a workaround in place (screenshot 4), but it should not be required ofcourse.
synapse workspace
git branch
after deployment using this devops task, it is passed as an integer, and the linkedservice shows an error (in this case, defaulting back to api version 45.0)
i am using this current workaround now to force it as a string:
for linked service property: when having a string in workspace (screenshot 1) , and in git (branch) it is still a string (screenshot 2), it gets deployed as an int in the deployed workspace (screenshot 3). i have a workaround in place (screenshot 4), but it should not be required ofcourse.
synapse workspace![image](https://github.com/Azure/Synapse-workspace-deployment/assets/3052927/4056ad0a-481f-4cfd-9499-dd4bd07a9913)
git branch![image](https://github.com/Azure/Synapse-workspace-deployment/assets/3052927/034dd7e4-a399-4142-b210-07296d77eee9)
after deployment using this devops task, it is passed as an integer, and the linkedservice shows an error (in this case, defaulting back to api version 45.0)![image](https://github.com/Azure/Synapse-workspace-deployment/assets/3052927/27141226-bc6c-4528-b51d-ce65eb3503ad)
i am using this current workaround now to force it as a string:![image](https://github.com/Azure/Synapse-workspace-deployment/assets/3052927/8375af56-7b61-4468-bd96-2344d1cbe00e)