Azure / Azure/Synapse-workspace-deployment

json string gets deployed as int property

Open
#94 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
29
Forks
50
PR merge metrics
No merged PRs in 30d

Description

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.

1. synapse workspace
![image](https://github.com/Azure/Synapse-workspace-deployment/assets/3052927/4056ad0a-481f-4cfd-9499-dd4bd07a9913)

2. git branch
![image](https://github.com/Azure/Synapse-workspace-deployment/assets/3052927/034dd7e4-a399-4142-b210-07296d77eee9)

3. 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)

4. 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)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the deployment with the linked service property shown in the workspace and Git branch screenshots, then compare the deployed value with the source value. Done means the property remains a string after deployment and the linked service no longer reports the API-version error without requiring the reported workaround.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, typescript
Domain
cloud, devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.