Skip to content
This repository has been archived by the owner on Aug 21, 2024. It is now read-only.

Add AWS image name parser #35

Merged
merged 1 commit into from
Oct 11, 2022
Merged

Add AWS image name parser #35

merged 1 commit into from
Oct 11, 2022

Conversation

major
Copy link
Member

@major major commented Oct 10, 2022

Parse additional information about AWS images using their name.

Fixes #34

Signed-off-by: Major Hayden major@redhat.com

Parse additional information about AWS images using their name.

Fixes #34

Signed-off-by: Major Hayden <major@redhat.com>
@major major force-pushed the parse-aws-image-names branch from 82e4eb9 to da2f223 Compare October 10, 2022 18:36
Copy link
Member

@F-X64 F-X64 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've tried to break that regex as hard as I could and failed.
Great job ;)

@major
Copy link
Member Author

major commented Oct 11, 2022

@FKolwa Hah, thanks. I kept thinking I could get creative with splitting on dashes and underscores, but then I realized that it would be easier with a regex of some sort. 🤷🏻‍♂️

@major major merged commit 3479850 into main Oct 11, 2022
@major major deleted the parse-aws-image-names branch October 11, 2022 11:17
@F-X64
Copy link
Member

F-X64 commented Oct 11, 2022

Btw. Who decides about this naming strategy? Is it Red Hat? Is it Amazon? Is there some guarantee that future image names will adhere to this or could we end up with a "rhel-9.1_amazing_blueberry-HVM-HOURLY-2023" at some point?

@major
Copy link
Member Author

major commented Oct 11, 2022

That's a good question. Based on what I've seen so far for hourly/cloud access, it looks like we are the ones that decide.

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

Successfully merging this pull request may close these issues.

Get extra image data from AWS image names
2 participants