[#IOPSC-81] Trace ApiKey existence on Service creation #224
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.
List of Changes
has_primary_key
andhas_secondary_key
attribute onapi.services.create
tracing event`
Motivation and Context
We have feedback of Services created correctly but the payload does not contain the ApiKey. This PR introduces a traces so that we can have evidence of the bug
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: