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

Unable to create Pipeline: Value cannot be null. Parameter name: Path #143

Open
MarcoDelGamba opened this issue Nov 24, 2023 · 3 comments
Open

Comments

@MarcoDelGamba
Copy link

MarcoDelGamba commented Nov 24, 2023

Hi all,

I am currently trying to create a pipeline with a PAT token with full access:

var (
	AzDoEnvironmentPipelineName   = "test"
	AzDoEnvironmentPipelineFolder = "Applications"
	AzDoEnvironmentOrgName = "xxx"

	AzDoEnvironmentProjectName = "xxx"
)	

// inside a function	
CreatePipelineConfigurationParameters := pipelines.CreatePipelineConfigurationParameters{
	Type: &pipelines.ConfigurationTypeValues.Yaml,
}
CreatePipelineParameters := pipelines.CreatePipelineParameters{
	Name:          &AzDoEnvironmentPipelineName,
	Folder:        &AzDoEnvironmentPipelineFolder,
	Configuration: &CreatePipelineConfigurationParameters,
}

pipeline, err := pipelineClient.CreatePipeline(ctx, pipelines.CreatePipelineArgs{
	Project:         &AzDoEnvironmentProjectName,
	InputParameters: &CreatePipelineParameters,
})
if err != nil {
	fmt.Println("Error creating pipeline:", err)
	os.Exit(1)
}

However, this error is printed:

Error creating pipeline: Value cannot be null.Parameter name: Path

Checking on the library docs i am not able to find "Path" anywhere

Is this a bug?

Expected behavior: I expect it to work or at least have a clearer error message

@francisconunesnavarro
Copy link

I also have this problem, thanks for PR @MarcoDelGamba

@tedchamb or @SilverdewBaker could you please review this pull request?

@mrpr0p3r
Copy link

I see this is a pretty common problem!
Is it possible to review this PR? It would help me too!

@cbl315
Copy link

cbl315 commented Aug 6, 2024

Any update for this issue?
The issue is still exist in API version 7.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants