Azure / Azure/azure-powershell

Remove-AzDataFactoryV2Dataset Return Question

Open
#22,040 4 comments 0 reactions 0 assignees View on GitHub
act-codegen-extensibility-squad customer-reported Data Factory question Service Attention
Dominant language
C#
Stars
4.8k
Forks
4.3k
Avg merge
3d 14h
Merged PRs (30d)
54

Description

### Description

Remove-AzDataFactoryV2Dataset Documentation states return is [void], which is what I observe in use and don't like one bit.

A bool as per Remove-AzDataFactoryV2Pipeline would be much better as this makes it much easier to reliably handle ADF cleaning before deployments.

My question is why the docs here:
https://github.com/Azure/azure-powershell/blob/main/src/DataFactory/DataFactoryV2/help/Remove-AzDataFactoryV2Dataset.md

Do in fact describe the bool return for this cmdlet. So which is correct?

### Script or Debug output

_No response_

### Environment data

_No response_

### Module versions

```PowerShell
F:\posh\exps> get-module Az*

ModuleType Version PreRelease Name ExportedCommands
---------- ------- ---------- ---- ----------------
Script 2.10.4 Az.Accounts {Add-AzEnvironment, Clear-AzConfig, Clear-AzContext, Clear-AzDefault…}
Script 1.16.11 Az.DataFactory {Add-AzDataFactoryV2DataFlowDebugSessionPackage, Add-AzDataFactoryV2Trig…
Script 6.5.0 Az.Resources {Export-AzResourceGroup, Export-AzTemplateSpec, Get-AzDenyAssignment, Ge…
```

### Error output

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with src/DataFactory/DataFactoryV2/help/Remove-AzDataFactoryV2Dataset.md and compare its documented return value with the observed Remove-AzDataFactoryV2Dataset behavior and the Remove-AzDataFactoryV2Pipeline command. Confirm which return contract is intended, then update the documentation or implementation consistently and verify the result against the reported deployment-cleanup use case.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
cli, cloud, documentation
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.