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

aws-sdk-go/service/scheduler DeleteSchedule "ValidationException: ClientToken cannot be empty" #4701

Open
dontirun opened this issue Jan 24, 2023 · 3 comments
Labels
bug This issue is a bug. p2 This is a standard priority issue

Comments

@dontirun
Copy link

Describe the bug

Using the scheduler DeleteSchedule function without a ClientToken always results in ValidationException: ClientToken cannot be empty.

The DeleteSchedule Command should be auto generating a ClientToken when not specified.

Expected Behavior

The SDK generates a unique ClientToken for me instead of having to specify one

Current Behavior

Using this method without specifying the ClientToken produces a ValidationException.

Reproduction Steps

package main

import (
	"fmt"

	"github.com/aws/aws-sdk-go/aws"
	"github.com/aws/aws-sdk-go/aws/session"
	"github.com/aws/aws-sdk-go/service/scheduler"
)

func main() {
	mySession := session.Must(session.NewSession())
	sch := scheduler.New(mySession)
	_, err := sch.DeleteSchedule(&scheduler.DeleteScheduleInput{Name: aws.String("foo")})
	if err != nil {
		fmt.Println(err)
	}
}

Possible Solution

No response

Additional Information/Context

Seems related to this aws/aws-sdk-js-v3#4212

SDK version used

v1.44.185

Environment details (Version of Go (go version)? OS name and version, etc.)

go version go1.19 darwin/arm64

@dontirun dontirun added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Jan 24, 2023
@dontirun
Copy link
Author

Same error on DeleteScheduleGroup as well

@aajtodd
Copy link
Contributor

aajtodd commented Jan 25, 2023

Thanks for the report. This appears to be a bug affecting both restJson and restXml protocols when the target field location is anything other than the body.

@aajtodd aajtodd removed the needs-triage This issue or PR still needs to be triaged. label Jan 25, 2023
@RanVaknin RanVaknin self-assigned this Feb 3, 2023
@RanVaknin RanVaknin added the investigating This issue is being investigated and/or work is in progress to resolve the issue. label Feb 3, 2023
@RanVaknin RanVaknin added the p2 This is a standard priority issue label Mar 30, 2023
@EliaBracciSumo
Copy link

@RanVaknin @aajtodd any update on this?

@lucix-aws lucix-aws removed the investigating This issue is being investigated and/or work is in progress to resolve the issue. label Dec 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. p2 This is a standard priority issue
Projects
None yet
Development

No branches or pull requests

5 participants