feat: Change default isolation mode from 'restrictive' to 'cfg' #345
+4
−4
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.
Closes: #338
Summary
This PR changes the default isolation mode from 'restrictive' to 'cfg' to provide better workspace isolation by default.
Changes Made
arg_parser.py
--im restrictive
where the restrictive mode behavior is specifically being testedWhy This Change?
The 'cfg' isolation mode provides better workspace isolation by creating/updating an ansible.cfg file in the current working directory. This approach is more user-friendly and provides clearer workspace boundaries compared to the 'restrictive' mode.
Testing
--im
flagImpact
--im restrictive
if needed