All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
- Defined ignored types in references and added
BigDataPool
to it #289
- Validation of ADF files fails when JSON contains property with single quote #287
- Validation of ADF files fails when a pipeline has reference to Synapse notebook
- Support for new SynapseNotebook activity #279
- Version 1.0 released
- 100% tests passed
- Bug #260: Test-AdfCode function: The property 'globalParameters' cannot be found on this object.
- Bug #226: Cannot overwrite/set DateTime type of value via config file
- Bug #229: Wildcard in name not working in json config file
- The module accepts Credentials type of object (when loading from files), but the deployment is skipped and not supported yet. #156
Publish-AdfV2UsingArm
cmdlet to make it compatible with PS 5.1- Updating value of global params of boolean types #203
- Added tests for
Publish-AdfV2UsingArm
- Added
OutputFolder
input parameter toExport-AdfToArmTemplate
- Added new cmdlet:
Test-AdfArmTemplate
#191
- Bug: Error in replacing property using config.csv when empty element exists #186
- Bug: Replacing properties from json-config for managedPrivateEndpoints #184 #185
- Bug fixed: Loading ADF from code fails when excluding any object and ManagedVNET exist #171
- Added structure to return object for Test-AdfCode which allows to check number of warnings too
- Fixed tests
- Fixed bug: add 'properties' node to ManagedVirtualNetwork if does not exist in default.json file #157
- Added cmdlet:
Export-AdfToArmTemplate
- Added cmdlet:
Publish-AdfV2UsingArm
(preview) - Fixed
Test-AdfCode
which complete exec even if some issue is found - Added workaround for ManagedVirtualNetwork object without 'properties' node #149
- Fixed #147: Pipeline could be broken when contains array with 1 item in JSON file and any property was updated
- Added cmdlet to generate mermaid diagram to be used in MarkDown type of documents
- Added public command
Start-AdfTriggers
- Added retry action on failure of starting trigger #107
- Fixed
Get-ReferencedObjects
which fails for files with empty element in JSON #128
- Fixed
Test-AdfCode
when validating empty factory #125
- Cmdlet
Test-AdfCode
validates config files #62 - Support configuration for Managed Private Endpoint #95
- Implement Dry Run Functionality for Publishing #120 (Thanks Liam!)
- Added option to index into arrays by element name #98 (Thanks Niall!)
- Removing excluded ADF objects when option $DoNotDeleteExcludedObjects = $false (#108)
- Changed method of discovering referenced objects (Get-ReferencedObjects) #95
- Support for ADF Managed Virtual Network & Managed Private Endpoint (preview)
- Deploy global Parameter type object (#92)
- Cmdlet
Test-AdfCode
returns number of found errors.
- Add Test method for Linked Services (#48) Preview
- JSON file corrupted when contained object is located deeper than 15 nodes ([#80])
- New function: Test-AdfCode #62]
- Better control of which: (see new publish flags below)
- triggers could be stop/start
- objects could be removed (if apply)
- Publish flag:
DoNotDeleteExcludedObjects
(#47) - Publish flag:
DoNotStopStartExcludedTriggers
allows stopping selected triggers (#51) - Numbers to all error messages (full list)
- Do not start trigger which has not been deployed and thus does not exist (#51)
- Support wildcard when specifying object(s) name in config file (#58)
- Added option
$IgnoreLackOfReferencedObject
(#64) - Add object name to the msg before action (#49)
- Exit publish cmd when ADF name is already in use (#43)
- Allow selecting objects in given folder (#68)
- Finding dependencies miss objects when the same object names occurs (#65)
- DeleteNotInSource fails when attempting to remove active trigger or found many dependant objects (#67)
- Added the ability to only warn on missing paths in config (#59 by @chris5287)
- JSON file could be corrupted when config update has happened on a very deep path (#33)
- Special characters deployed wrong (#50)
- Added new publish option: FailsWhenConfigItemNotFound
- Bug during a publication when General Parameters are not existed (#39)
- Bug in GetObjectsByFolderName when General Parameters are not existed (#38)
- Added public function: Stop-AdfTriggers
- Support of JSON format for config files
- Support of Global Parameters (#29)
- Function GetObjectsByFolderName (Adf class) uses LIKE operator (#31)
- Removed workaround for deployment of Azure Integration Runtimes.
- List of filtering rules (Includes/Excludes) can be provided by file
- Config file allows defining a property to be added or removed
- All lines were being ignored in config file after commented line (#24)
- Precise error message once path provided in config file cannot be found in json file
- Config file allows using tokens in
value
column to be replaced by environment variables value
- Validates config file during loading when
stage
parameter is provided - Config files allows defining whole nested JSON object (in addition to string or number only) (#16)
- A line in CSV config file can be commented with hash character
- DeleteNotInSource option is $false by default now
- Creates copy of files when replacing properties with values from config
- When DeleteNotInSource=True and a trigger vanished from the source then the active trigger was not removing from service (#17)
- Starting triggers based on properties replaced within config values (#18)
- Encoding UTF8 is set when reading all objects from disk (#19)
- Changed encoding to UTF8 when writing files with replaced properties
- Additional method of deployment by New-AzResource cmdlet (default)
- Correct casing for folder "linkedService" in Import-AdfObjects cmdlet
- Creation of ADF (if does not exist) is optional now
- The first set of unit tests for the module
- Capability to pass full path to csv config file location via
stage
parameter
- Fixed RegEx to scanning dependant objects (references). They were not found when multiple whitespaces figured.
- Function
Import-AdfFromFolder
throws an exception when passed folder doesn't exist.
- Capability to publish only objects located in the selected folder(s) in ADF
- Function
Import-AdfFromFolder
is public now. Return instance of ADF class - Functions in ADF class allows returning a list of objects by name or folder
- Function
- Restarting triggers fails for Tumbling Window type of Trigger [#4]
- Filtering (include or exclude) objects to be deployed by name and/or type
- Publish options allow you to control:
- Whether stop and restarting triggers
- Whether delete or not objects not in the source
- Drop objects not in the source
- New function: Get-AdfFromService
- Supports different objects with the same name
- Stop-Triggers : The property 'Count' cannot be found on this object. Verify that the property exists. (#2)
- PS module reads only ps1 files as cmdlets during its loading
- Support (deployment) of Azure Managed Integration Runtimes
- Support (deployment) of Integration Runtimes type of connections (inc. Self-Hosted only)
- Support (deployment) of triggers, including stop/start
- Skip importing particular type of objects when folder doesn't exist
- Location is required when ADF instance doesn't exist and need to be created
- Az.DataFactory minimum version 1.7.0 is required
- Added support of dataflows
- Shows Elapsed time at the end of publish process
- Replace property values defined in csv config file (per environment)
- Deploy ADF from code written in JSON files
- Deployment process takes care of the order in which files are deployed