Bug Description
When using the SAM cli the sam eval... command is incompatible with the file structure created by sam init. It looks for a structure that contains .configs/... but the initialization structure is configs/....
Once this issue is resolved there is also a bug that causes the local .env variables to not be loaded at the proper time for local evals.
Fixes can be found here #1198
Expected Behavior
SAM evals should default to look for configuration items in the same directory structure as the sam init command generates.
SAM evals should properly pick up the .env variables for things like broker host before continuing to execute the evals themselves.
Steps to Reproduce
Install the latest SAM whl. Run any local eval with a command like sam eval evals/blog/blog-test_suite.test.json, you can copy the tests from the examples section of the solace agent mesh src repo.
Solace Broker version
n/a
Solace API
n/a
Solace API version
n/a
Bug Description
When using the SAM cli the
sam eval...command is incompatible with the file structure created bysam init. It looks for a structure that contains.configs/...but the initialization structure isconfigs/....Once this issue is resolved there is also a bug that causes the local .env variables to not be loaded at the proper time for local evals.
Fixes can be found here #1198
Expected Behavior
SAM evals should default to look for configuration items in the same directory structure as the sam init command generates.
SAM evals should properly pick up the .env variables for things like broker host before continuing to execute the evals themselves.
Steps to Reproduce
Install the latest SAM whl. Run any local eval with a command like
sam eval evals/blog/blog-test_suite.test.json, you can copy the tests from the examples section of the solace agent mesh src repo.Solace Broker version
n/a
Solace API
n/a
Solace API version
n/a