-
Notifications
You must be signed in to change notification settings - Fork 226
Fixes #38241 - Extend userdata API by MAC address endpoint #912
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
Merged
+15
−0
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at the method this feels like an abuse of the API:
smart-proxy/modules/templates/userdata_proxy_request.rb
Line 5 in 6624f2c
Technically it may work since it calls
flatten, but I really don't likeflattenbecause it ends up being really unpredictable what gets called.But that's probably not the real issue. If you look at
ProxyRequestyou can see it copies the parameters while removing a blacklist:smart-proxy/modules/templates/proxy_request.rb
Lines 30 to 33 in 6624f2c
Looking at that blacklist, we can see
kindis in there:smart-proxy/modules/templates/proxy_request.rb
Line 9 in 6624f2c
I suspect both
macandkindare inparams. Not entirely sure what the correct thing to do here, but this whole API feels awkward.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alright, I see why
hostgroupandtemplatedon't need to be added in the test - thanks!However, to make this API feel less awkward I see two improvements currently:
a.) Add another function in
UserdataProxyRequestto mitigate theflattenhere?Like a
def get_macand then put themacas mandatory function parameter? But, this makes it less generic..b.) Overwrite BLACKLIST_PARAMETERS when inheriting
ProxyRequestand addmacthere?What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ekohl thoughts on the comment from Bastian?