HPCC-32198 Dali disable default file user option needs support in config files

[kenrowland]

Added support to ensure option is valid and copied to environment

Signed-Off-By: Kenneth Rowland [email protected]

Type of change:

• This change is a bug fix (non-breaking change which fixes an issue).
• This change is a new feature (non-breaking change which adds functionality).
• This change improves the code (refactor or other change that does not change the functionality)
• This change fixes warnings (the fix does not alter the functionality or the generated code)
• This change is a breaking change (fix or feature that will cause existing behavior to change).
• This change alters the query API (existing queries will have to be recompiled)

Checklist:

• My code follows the code style of this project.
  • My code does not create any new warnings from compiler, build system, or lint.
• The commit message is properly formatted and free of typos.
  • The commit message title makes sense in a changelog, by itself.
  • The commit is signed.
• My change requires a change to the documentation.
  • I have updated the documentation accordingly, or...
  • I have created a JIRA ticket to update the documentation.
  • Any new interfaces or exported functions are appropriately commented.
• I have read the CONTRIBUTORS document.
• The change has been fully tested:
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • I have checked that this change does not introduce memory leaks.
  • I have used Valgrind or similar tools to check for potential issues.
• I have given due consideration to all of the following potential concerns:
  • Scalability
  • Performance
  • Security
  • Thread-safety
  • Cloud-compatibility
  • Premature optimization
  • Existing deployed queries will not be broken
  • This change fixes the problem, not just the symptom
  • The target branch of this pull request is appropriate for such a change.
• There are no similar instances of the same problem that should be addressed
  • I have addressed them here
  • I have raised JIRA issues to address them separately
• This is a user interface / front-end modification
  • I have tested my changes in multiple modern browsers
  • The component(s) render as expected

Smoketest:

• Send notifications about my Pull Request position in Smoketest queue.
• Test my draft Pull Request.

Testing:

[github-actions]

Jira Issue: https://hpccsystems.atlassian.net//browse/HPCC-32198

Jirabot Action Result:
Workflow Transition: Merge Pending
Updated PR

[jakesmith]

@kenrowland - looks good. Should this target 9.6.x?

[kenrowland]

@jakesmith
I would have to check when the option was added, however since no one is likely using it since it was not documented, I believe that 9.8.x is fine. Making sure it is available is part of my overall solution/recommendations for analyzing the effects of removing the "Authenticated Users" group as a default file scope permission. This, the recent cache fix, and some potential logging changes will allow dev ops to analyze their potential impact when the group is removed. That way they can mitigate as much as they can before removal.

[jakesmith]

@kenrowland - please retarget - there's expectations that it will be in 9.6, that they are about to upgrade to, and want the ability to use this option (if they need to)

[kenrowland]

@jakesmith retargeted to candidate-9.6.x as requested

[jakesmith]

@kenrowland - looks good.

[kenrowland]

@ghalliday please merge