Proposed changes

Change the default processing order of artifacts included in a device profile operation, where configuration is processed before software. The new order supports more use-cases out-of-the-box.

Technically this is a breaking change as it changed the behaviour, however we believe it will only positively impact users and remove common annoyances with the existing processing order.

Old Processing Order

• Firmware
• Software
• Configuration

New Processing Order

• Firmware
• Configuration
• Software

Below lists the advantages and disadvantages of the change:

Advantages

• Repositories can be configured (with credentials or proxy settings) before applications/containers are installed via software
• Configuration can be applied before the application/container starts the first time (also removes need for restarting the software)

Disadvantages

• Short period of time where potentially incompatible configuration is applied before the new application version has been installed
• Potential that application could overwrite config (generally only occurs if app builders haven't defined the linux package definition correctly)

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
• Documentation Update (if none of the other choices apply)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

#3684

Checklist

• I have read the CONTRIBUTING doc
• I have signed the CLA (in all commits with git commit -s. You can activate automatic signing by running just prepare-dev once)
• I ran just format as mentioned in CODING_GUIDELINES
• I used just check as mentioned in CODING_GUIDELINES
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments