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
(logs): Importing log group ignores region #18214
Comments
When log group is imported it is crucial to preserve an information about region where log group exists. Without that information it is not possible to implement cross region logging. fixes aws#18214
Hey @kornicameister, Thank you for reporting this, and thank you for submitting a fix! Before someone takes a look at your PR, I see the listed CLI version is 1.134. Have you confirmed your published fix with the v2 library? 😸 😷 |
Actually, I haven't thought about that. I just copied details from an issue we ( or more like @skinny85 who confirmed that issue exists) found this one in. |
@NGL321 apart from the fact I have submitted a PR against master I don't know how to publish a change against v2. |
The change will make it to v2 automatically - we have an automated job that merges |
When log group is imported it is crucial to preserve an information about region where log group exists. Without that information it is not possible to implement cross region logging. fixes #18214 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
When log group is imported it is crucial to preserve an information about region where log group exists. Without that information it is not possible to implement cross region logging. fixes aws#18214 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
What is the problem?
Per this comment
Blocks: #17747
Reproduction Steps
Same as in #
What did you expect to happen?
When imported log group's region is referenced incorrect region is taken into account. A region coming from log group's ARN ought to be taken into account instead of region of the stack.
What actually happened?
Region of the stack where log group is imported in is taken into account.
CDK CLI Version
1.134
Framework Version
No response
Node.js Version
17.1.0
OS
Linux
Language
Typescript, Python, .NET, Java, Go
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: