-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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-cdk-lib: SplunkLogDriverProps does not accept token value #21744
Comments
Are you making use of the |
I’m trying to use “token” because the error messages say that token will be used if secretToken is not specified. If that’s not the case, the messages should be updated. |
I've created a PR for this @karlkranich |
Thank you! |
`token` is no longer a valid option in v2, so `secretToken` is required by virtue of needing to provide at least one of `token` or `secretToken` Removed test which checks for error because `secretToken` is now required so we cannot check for error, even with `testDeprecated` to my knowledge fixes #21744 ---- ### All Submissions: * [ ] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) ### Adding new Unconventional Dependencies: * [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-new-unconventional-dependencies) ### New Features * [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)? * [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
`token` is no longer a valid option in v2, so `secretToken` is required by virtue of needing to provide at least one of `token` or `secretToken` Removed test which checks for error because `secretToken` is now required so we cannot check for error, even with `testDeprecated` to my knowledge fixes aws#21744 ---- ### All Submissions: * [ ] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) ### Adding new Unconventional Dependencies: * [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-new-unconventional-dependencies) ### New Features * [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)? * [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Describe the bug
When trying to provide a token to the SplunkLogDriver, I would like to provide the token as a string value as I did with CDKv1. CDK 2.38.1 internal errors say "Please provide either token or secretToken" and that if "secretToken" is not provided, that "token" will be used. But if token is provided, it says," 'token' does not exist in type 'SplunkLogDriverProps' ".
Expected Behavior
Should be able to provide "token" or "secretToken" in SplunkLogDriver props.
Current Behavior
If "token" is provided, get: Object literal may only specify known properties, and 'token' does not exist in type 'SplunkLogDriverProps'.
Reproduction Steps
Provide a token to SplunkLogDriver, and do not provide secretToken.
Possible Solution
Allow specifying "token" as with CDK v1.
Additional Information/Context
No response
CDK CLI Version
2.38.1
Framework Version
No response
Node.js Version
16.16.0
OS
macOS 12.5.1
Language
Typescript
Language Version
TypeScript 4.7.4
Other information
No response
The text was updated successfully, but these errors were encountered: