question

$$ANON_USER$$ avatar image
0 Votes"
$$ANON_USER$$ asked JamesPerry-6446 answered

Synapse Analytics Workspace CI/CD - Publishing with Custom Parameter Template

We are experiencing unexpected behavior trying to implement a custom parameter template (template-parameters-definition.json) per the documentation. Values, ex. pipeline parameters, defined are not populated when deploying causing validation errors in the target workspace. Is anyone successfully using custom parameters for promoting workspace artifacts to environments?


azure-synapse-analytics
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello anonymous user and welcome to Microsoft Q&A.

If the current values are not being used as default values, then it is likely your custom parameter template is using - . - tells Data Factory to not use default value, and instead require a user-provided value during promotion.

There is one other thing to check, secureString types. If it was possible to extract the value of a secureString, then it wouldn't be secure. Hence, secureString types do not generate default values.

Does this help, or have I missed the ask?

0 Votes 0 ·

Hi, @MartinJaffer-MSFT,

Thanks for the response. I may not have been clear enough with my question. Yes, the template used '-' but the provided values, via the 'OverrideParameters' of the Synapse workspace deployment pipeline task, don't seem to be passed in the workspace deployment and then have empty values which then don't validate. I also tried, as a test, just using the example template from the documentation but that threw a 'Error: Checkstatus => status: 500; status message: Internal Server Error' for the the AutoResolveIntegrationRuntime.

Is there any further documentation or perhaps some examples to reference?

Thanks.
John

0 Votes 0 ·

1 Answer

JamesPerry-6446 avatar image
0 Votes"
JamesPerry-6446 answered

I had a similar issue, i actually removed the integration runtime section from the json file and also had an issue with linked services so amended that slightly too. The file that we used successfully which included exposing parameters from the pipelines is attached but needs the extension renaming obvs.114634-template-parameters-definition.txt



· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@JamesPerry-6446 Thanks! I'll take a look, really appreciate your insight.

0 Votes 0 ·