setup:static-content:deploy --dry-run incorrectly creates requirejs-config.js files

[davidalger]

When running the CLI tool in Magento 2 and specifying the --dry-run flag, nothing should be altered by the tool. This flag fails to suppress creation of the requirejs-config.js files when --dry-run is specified.

Versions affected: Magento 2.1.x, 2.0.x.

The following steps to reproduce are run against Magento 2.1.1.

$ rm -rf pub/static
$ magento setup:static-content:deploy --dry-run  --no-javascript --no-css --no-less --no-images --no-fonts --no-html --no-misc --no-html-minify
Requested languages: en_US
Requested areas: frontend, adminhtml
Requested themes: Magento/blank, Magento/luma, Magento/backend
Dry run. Nothing will be recorded to the target directory.
Dry run. Nothing will be recorded to the target directory.
Dry run. Nothing will be recorded to the target directory.
=== frontend -> Magento/luma -> en_US ===
.
Successful: 1 files; errors: 0

---

New version of deployed files: 1473348444
=== frontend -> Magento/blank -> en_US ===
=== adminhtml -> Magento/backend -> en_US ===
..
Successful: 1 files; errors: 0

---

New version of deployed files: 1473348444

Successful: 1 files; errors: 0

---

New version of deployed files: 1473348444
$ tree pub/static
pub/static
└── _requirejs
    ├── adminhtml
    │   └── Magento
    │       └── backend
    │           └── en_US
    │               └── requirejs-config.js
    └── frontend
        └── Magento
            ├── blank
            │   └── en_US
            │       └── requirejs-config.js
            └── luma
                └── en_US
                    └── requirejs-config.js

11 directories, 3 files
$ magento -V
Magento CLI version 2.1.1 

As you can see, by removing the entire pub/static directory and then running the setup:static-content:deploy command with --dry-run specified, three files were created by the tool.

[davidalger]

@veloraven May be good to address #4961 at the same time as this one.

[IlnitskiyArtem]

@davidalger, thanks for reporting this issue. Created internal issue MAGETWO-70454 to investigate and track this issue.

[magento-engcom-team]

@davidalger, thank you for your report.
We've created internal ticket(s) MAGETWO-70454 to track progress on the issue.