Adds explicit id for faas entities #2393 #2404
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
thompson-tomo
force-pushed
the
feature/#2393_faasId
branch
from
e7a6803 to
007c916
Compare
lmolkova
moved this from Untriaged
to Awaiting SIG approval
in Semantic Conventions Triage
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
|
Awaiting review |
Signed-off-by: James Thompson <[email protected]>
thompson-tomo
force-pushed
the
feature/#2393_faasId
branch
from
007c916 to
6d1d0e9
Compare
|
@trisch-me another pr which is a pure ecs migration. :) |
trisch-me
reviewed
Jul 30, 2025
trisch-me
reviewed
Jul 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #2393
Changes
Adds in an explicit id for the faas entity to enable decoupling of the cloud resource.id
Note: if the PR is touching an area that is not listed in the existing areas, or the area does not have sufficient domain experts coverage, the PR might be tagged as experts needed and move slowly until experts are identified.
Merge requirement checklist
[chore]