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

Fixes #32014 - Expose Shellhooks as a proxy feature #25

Merged
merged 3 commits into from
Mar 8, 2021

Conversation

adamruzicka
Copy link
Contributor

No description provided.

@@ -0,0 +1,6 @@
# frozen_string_literal: true

proxy_feature = Feature.where(name: 'Shellhooks').first_or_create
Copy link
Member

Choose a reason for hiding this comment

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

@adamruzicka , does the name make difference, i.e. 'Shellhooks' vs 'ShellHooks'?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It can be anything as long as its lower case version matches shellhooks

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We could maybe even split it into two words

Copy link
Member

Choose a reason for hiding this comment

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

I asked because I don't really know if the name affects anything (like some magic that loads gem by it's name or constants). Looking at other examples of exposing, this looks OK and can be merged.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Nothing crazy like that. It gets downcased, whitespace thrown out and then it gets matched against whatever the proxy returns as its features.

Copy link
Member

Choose a reason for hiding this comment

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

Then I guess it's safe to merge.

Copy link
Member

@ofedoren ofedoren left a comment

Choose a reason for hiding this comment

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

Thanks, @adamruzicka, merging.

@ofedoren ofedoren merged commit 4de6e83 into theforeman:master Mar 8, 2021
@adamruzicka adamruzicka deleted the proxy-feature branch March 8, 2021 09:58
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.

2 participants