azure-ai-ml CommandComponent hash does not include additional_includes files/dirs

[terminatur]

Is your feature request related to a problem? Please describe.
The hash for determining a components uniqueness does not include the additional includes. I have a scenario where I don't use the code property and only use additional_includes as I only want to upload a subset of my code. When I submit an experiment job to an AML workspace using local components the code changes are not detected, so the job runs with an older version of the code.

Describe the solution you'd like
Inside _cache_utils.py parse the files / directories listed under additional_includes.

Describe alternatives you've considered
As a work around I figured out I can include a random uuid in the tags section. This forces an upload every time. If I have time I could compute the hash on the additional_includes file/directories and add that as a tag to still use the caching mechanism.

Additional context
Add any other context or screenshots about the feature request here.

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/azure-ml-sdk @azureml-github.

[github-actions]

Hello @terminatur. I'm an AI assistant for the azure-sdk-for-python repository. I have some suggestions that you can try out while the team gets back to you.

• Consider updating the hashing logic in _cache_utils.py so that it iterates over the files and directories specified in additional_includes and computes a combined hash. This change would allow local component changes (when not using the code property) to be detected automatically.

• As a workaround, your approach of injecting a random UUID into the tags is a viable temporary solution, but a more robust solution would integrate the additional file states into the component hash calculation.

• Evaluate backward compatibility. If changes are made to the hashing mechanism, ensure that existing workflows that rely on the old behavior can be migrated smoothly or flagged with version checks.

• For additional context and examples on handling file inclusions across Azure SDK components, you may refer to the project’s README and feedback guidance at Azure SDK Issues and the Samples Repo.

The team will get back to you shortly, hopefully this helps in the meantime.

[kingernupur]

@terminatur Thank you for reporting this. We are looking into it.