Problem Description

1. While addingcoder_metadata blocks inside a module we need to pass the resource_id to link the metadata to. The issue arises when theresource_id of the instance is linked to an existingcoder_metadata block in the main template, which causes a conflict and the template fails to build.

2. Attempting to use an alternative identifier, such asagent_id, doesn't show metadata on the workspace page.

Steps to Reproduce

1. Add acoder_metadata block to a module and link it to theresource_id of an instance.
2. Add anothercoder_metadata block in the main template referencing the sameresource_id.
3. Observe the conflict in the failed build.
4. Attempt to useagent_id instead in the module and note the absence of display metadata.

Impact

• Limits the flexibility of the coder modules because of possible conflicts.

Next Steps

• Update the handling ofcoder_metadata to avoid conflicts between module-level and main template declarations when sharing the sameresource_id. One possible solution is to merge and append the newitem entries when we detect a conflict inresource_id.
• Investigate why theagent_id does not work withcoder_metadata.