Skip to content
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

Deploy ADF global configurations #241

Open
BeneHa opened this issue Nov 15, 2022 · 3 comments
Open

Deploy ADF global configurations #241

BeneHa opened this issue Nov 15, 2022 · 3 comments
Assignees
Labels
blocked No appropriate capability in Microsoft's underlying module enhancement New feature or request

Comments

@BeneHa
Copy link

BeneHa commented Nov 15, 2022

Hey,
it would be great if the plugin could deploy the ADF global configuration which was recently added:
https://techcommunity.microsoft.com/t5/azure-data-factory-blog/granular-billing-for-azure-data-factory/ba-p/3654600

"globalConfigurations": { "PipelineBillingEnabled": "true" }
This configuration is located in the factory file after the global parameters.
According to the logs at the moment only global parameters are deployed, but this configuration is a separate object at the same level like the parameters.

Update of x global parameters complete. Finished deploying object: [factory].[x]

Thanks for this awesome tool and best regards
Benedikt

@NowinskiK NowinskiK added the enhancement New feature or request label Nov 17, 2022
@NowinskiK NowinskiK added this to the v1.0 milestone Nov 19, 2022
@NowinskiK NowinskiK self-assigned this Nov 20, 2022
@NowinskiK
Copy link
Member

image

@NowinskiK
Copy link
Member

So far, I haven't seen any documentation shows how to deploy this property via automated CI/CD.
There is no example script in github repo: Azure-DataFactory/SamplesV2
Hence, I can't develop this for now. Let me know once you find something.

@josephniblo
Copy link
Contributor

I've had some success deploying globalConfiguration using the API.

Although it's not documented, the factories GET request response includes the globalConfigurations, and the PUT request seems to set it correctly, too.

Unfortunately, since there's no globalConfigurations endpoint, I'm having to set the whole of properties - I've been firing off a GET, appending a globalConfigurations property and then sending back the PUT.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked No appropriate capability in Microsoft's underlying module enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants