ENT-10199: Fixed a bug regarding the resolution of namespaces inside function-calls#6213
ENT-10199: Fixed a bug regarding the resolution of namespaces inside function-calls#6213SimonThalvorsen wants to merge 1 commit into
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
|
@cf-bottom Jenkins please :) |
|
Alright, I triggered a build: Jenkins: https://ci.cfengine.com/job/pr-pipeline/14098/ Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-14098/ |
|
In your commit message I think it would be nice to enumerate the functions for which this is now fixed. |
Also, functions is a bit vague, i assume it means policy functions (not internal C functions). |
olehermanse
left a comment
olehermanse
left a comment
There was a problem hiding this comment.
Please look into the NULL scope / bundle, and also improve the changelog entry.
…function-calls Ticket: ENT-10199 Changelog: Title Signed-off-by: Simon Halvorsen <simon.halvorsen@northern.tech>
SimonThalvorsen
changed the title
nickanderson
left a comment
nickanderson
left a comment
There was a problem hiding this comment.
I am still missing an enuymerated list of policy functions that are affected by the change. I see in your comments read_module_protocal() but I think we should surface the specific list.
I changed the wording since as far as I could tell, it would affect all cases of expanding args inside a call, tested it with other functions also referencing variables in other bundles in the same non-default namespace and they all got the same issue without the fix, so rather than enumerating all functions I tried making the changelog-message more generic. But it may need some work to get this across more easily |
5 participants
Ticket: ENT-10199
Changelog: Title