Change Details

We need to make all of our puppet manifests able to be compiled with both the traditional and the future puppet parser. While at the moment it is possible to do this by adding a .configs file to the change, that won't work now that we want to sistematically check changes with the future parser. So do the following: * for every compiler run, compile the change with the future parser as well, save the produced files * when both the normal run and the one with the future parser work correctly, check the resulting catalog for diffs, add a link to it in the host page * if a parameter is defined in the CI job, run in "check for future mode", and report success only if the change compiles with both parsers with no diffs with production.

We need to make all of our puppet manifests able to be compiled with both the traditional and the future puppet parser. While at the moment it is possible to do this by adding a .configs file to the change, that won't work now that we want to sistematically check changes with the future parser. So do the following: * for every compiler run, compile the change with the future parser as well, save the produced files * when both the normal run and the one with the future parser work correctly, check the resulting catalog for diffs, add a link to it in the host page * if a parameter is defined in the CI job, run in "check for future mode", and report success only if the change compiles with both parsers with no diffs with production. Since we will expect future parser to run in the "future" environment, this depends on directory environments being available.

We need to make all of our puppet manifests able to be compiled with both the traditional and the future puppet parser. While at the moment it is possible to do this by adding a .configs file to the change, that won't work now that we want to sistematically check changes with the future parser. So do the following: * for every compiler run, compile the change with the future parser as well, save the produced files * when both the normal run and the one with the future parser work correctly, check the resulting catalog for diffs, add a link to it in the host page * if a parameter is defined in the CI job, run in "check for future mode", and report success only if the change compiles with both parsers with no diffs with production. Since we will expect future parser to run in the "future" environment, this depends on directory environments being available.