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

Use simple comparision instead of Contains / fix #20 #22

Merged
merged 1 commit into from
Oct 25, 2022

Conversation

yerfinojul
Copy link
Contributor

@yerfinojul yerfinojul commented Oct 24, 2022

When using strings.Contains our flow breaks when selecting the container - see issue #20
The problem is we have 2 containers that are named like this

  • sample-ui-logger
  • sample-ui

I pick up the first sample-ui, but it ends up ssh into sample-ui-logger, because .Contains function will match both in that case.

Please check it out, not sure there is a specific reason for using .Contains

@tedsmitt
Copy link
Owner

Thanks @yerfinojul! I don't think there is a reason why string.Contains - probably just poor coding on my part! Have tested the changes locally and LGTM! Merged 😄

tedsmitt pushed a commit that referenced this pull request Nov 1, 2022
tedsmitt pushed a commit that referenced this pull request Nov 1, 2022
tedsmitt pushed a commit that referenced this pull request Nov 12, 2022
tedsmitt added a commit that referenced this pull request Nov 21, 2022
* fix: #22 check PlatformFamily for nil value, as there is no default value for tasks of ec2 launch type

* fix: #21 lookup os family when task is ec2 launch type, avoid nil pointer ref when ec2 launch type

* fix: #21 add functions to determine underlying container os and set PlatformFamily to prevent nil reference

* test: #21 add tests for new functions
tedsmitt pushed a commit that referenced this pull request Jan 24, 2023
tedsmitt pushed a commit that referenced this pull request Jan 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants