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

describe-log-groups: --log-group-name-pattern does not list retentionInDays #8264

Closed
fauxbytes opened this issue Oct 25, 2023 · 3 comments
Closed
Assignees
Labels
closing-soon This issue will automatically close in 4 days unless further comments are made. logs p3 This is a minor priority issue service-api This issue is due to a problem in a service API, not the SDK implementation.

Comments

@fauxbytes
Copy link

Describe the bug

retentionInDays is missing from the listing when using --log-group-name-pattern.

Expected Behavior

Output should be the same when using --log-group-name-pattern as when using --log-group-name-prefix

Current Behavior

retentionInDays reported, when using --log-group-name-prefix

$ aws logs describe-log-groups --log-group-name-prefix '/aws/lambda/foo' --query 'logGroups[0].retentionInDays'
60

retentionInDays missing, when using --log-group-name-pattern

$ aws logs describe-log-groups --log-group-name-pattern 'foo' --query 'logGroups[0].retentionInDays'
null

Reproduction Steps

See above

Possible Solution

No response

Additional Information/Context

No response

CLI version used

aws-cli/2.13.21 Python/3.11.5

Environment details (OS name and version, etc.)

Windows/10 exe/AMD64

@fauxbytes fauxbytes added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Oct 25, 2023
@aBurmeseDev aBurmeseDev self-assigned this Oct 25, 2023
@aBurmeseDev aBurmeseDev removed the needs-triage This issue or PR still needs to be triaged. label Oct 25, 2023
@aBurmeseDev
Copy link
Member

aBurmeseDev commented Oct 25, 2023

Hi @fauxbytes - thanks for reaching out.

While researching, I came across this similar issue where the service team confirmed that this's expected behavior as mentioned in the docs like follows:

If you specify logGroupNamePattern in your request, then only arn, creationTime, and logGroupName are included in the response.

Hope that helps and please let me know if you have further questions!
John

@aBurmeseDev aBurmeseDev added closing-soon This issue will automatically close in 4 days unless further comments are made. service-api This issue is due to a problem in a service API, not the SDK implementation. logs p3 This is a minor priority issue and removed bug This issue is a bug. labels Oct 25, 2023
@fauxbytes
Copy link
Author

fauxbytes commented Oct 25, 2023

Thanks @aBurmeseDev.
That does clarify it. Appreciate you looking into it and finding an aswer for me.

In the context of user feedback (merely my opinion here): to me, logGroupNamePattern & logGroupNamePrefix look like they do quite the same thing: they are filter flags: One searches by prefix. The other - by substring. In that sense, I don't see the rationale of those returning different output. If there is one, I'd be keen to understand it. If there isn't, that's fine too, but I wouldn't call it 'expected behavior'.

@github-actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closing-soon This issue will automatically close in 4 days unless further comments are made. logs p3 This is a minor priority issue service-api This issue is due to a problem in a service API, not the SDK implementation.
Projects
None yet
Development

No branches or pull requests

2 participants