You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The run plugin feature for smithy cli will only pass along the model through standard input. To enable code generators in multiple target languages, it is beneficial for the run plugin to provide access to configuration on the smithy build file, such as library names, versions, and other code generation options. This should either be provided in the model as metadata or an environment variable should provide access to the smithy build json or this metadata.
I lean towards an option that has an ENV variable that contains a json string of arbitrary metadata that is a sibling to the run plugin. Example, given:
The run plugin feature for smithy cli will only pass along the model through standard input. To enable code generators in multiple target languages, it is beneficial for the run plugin to provide access to configuration on the smithy build file, such as library names, versions, and other code generation options. This should either be provided in the model as metadata or an environment variable should provide access to the smithy build json or this metadata.
https://smithy.io/2.0/guides/smithy-build-json.html#run-plugin
I lean towards an option that has an ENV variable that contains a json string of arbitrary metadata that is a sibling to the run plugin. Example, given:
perhaps ENV['SMITHY_PROJECTION_OPTIONS'] could be '{"foo": "bar"}'?
The text was updated successfully, but these errors were encountered: