feat: allow empty Memfault project key #31
Closed
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.

Summary
In cases where an upstream device uploads data to Memfault on behalf
of a downstream device, the project key is not required. This change
allows the project key to be optional in those cases. For the
NCS Memfault sources, this is when we are not using MDS or the
Memfault Zephyr HTTP client.
Test Plan
Confirmed that before this change, the build fails if the project key
is not set for a generic cortex-m application where Memfault is enabled:
Confirmed after this change, the build succeeds with this same build command.
Also confirmed that after this change, the build still fails if the project key
is not set for projects where MDS or the Memfault Zephyr HTTP client
are used:
and still succeeds when the project key is passed:
Resolve: MCU-982