Skip to content

Fix Amazon ECS Enums - #29871

Merged
o-nikolas merged 3 commits into
apache:mainfrom
Taragolis:fix-ecs-enum-str-comparasion
Mar 2, 2023
Merged

o-nikolas merged 3 commits into
apache:mainfrom
Taragolis:fix-ecs-enum-str-comparasion

Conversation

@Taragolis

Copy link
Copy Markdown
Contributor

Follow-up: #29761 (comment)

@boring-cyborg boring-cyborg Bot added area:providers provider:amazon AWS/Amazon - related issues labels Mar 2, 2023
@Taragolis
Taragolis requested a review from ferruzzi March 2, 2023 11:00
@Taragolis

Copy link
Copy Markdown
Contributor Author

I've just figure out that there is no tests for ECS Sensors 🙄

@Taragolis
Taragolis marked this pull request as draft March 2, 2023 17:41
@Taragolis
Taragolis force-pushed the fix-ecs-enum-str-comparasion branch from c958084 to 6274a9d Compare March 2, 2023 18:05

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Should we put this in a more general place so that other modules can make use of it?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Right now it just for fix but in general we could move it later if it useful for other places, that why I make it "private"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I was thinking the same thing. Seems like something we'll want to reuse.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Agree. We might want to do it now? It'd encourage others to use if needed instead of copy pasting it

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I feel like it is quite trivial to move it to a more generic place (and still keep it private if you'd prefer that). Seems easy to make the right choice now rather than having to fix it later. But I wont press any harder, happy to merge this as is and I can fix it in a follow up PR 👍

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I'd rather move it in separate PR when we actually need this functional. Just for avoid spending time to choose better name and better place 🤣

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Sounds good to me :)

@ferruzzi

ferruzzi commented Mar 2, 2023

Copy link
Copy Markdown
Contributor

Thanks for getting this so fast, I was planning to look at it this morning. 👍

LOL. I did a review and it wouldn't let me submit because Niko left the same two comments while I was typing. 👍

Co-authored-by: Niko Oliveira <onikolas@amazon.com>
@Taragolis
Taragolis marked this pull request as ready for review March 2, 2023 18:24

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I feel like it is quite trivial to move it to a more generic place (and still keep it private if you'd prefer that). Seems easy to make the right choice now rather than having to fix it later. But I wont press any harder, happy to merge this as is and I can fix it in a follow up PR 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:providers provider:amazon AWS/Amazon - related issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants