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
There are a number of things that don't get checked until runtime inside IOCs. At present we mostly rely on the schema helping us make sure our YAML is good when we are editing in a YAML checking editor.
Things we should do in the container build:
validate the schema of all support YAML
check support YAML for duplicate definition id's
check support YAML for database template references to non-existent files
ANYTHING ELSE?
Also it occurs to me that ec ioc validate for checking ioc instance yaml is woefully inadequate. At present it gets a container with a schema checker in it.
It would be far more instructive to instead fetch the generic IOC container it refers to and check it can generate the runtime assets inside of that - and launch the binary. That would pick up all possible errors that can occur. Including those that are currently missing.
This issue supersedes #170 so will be closing that.
The text was updated successfully, but these errors were encountered:
There are a number of things that don't get checked until runtime inside IOCs. At present we mostly rely on the schema helping us make sure our YAML is good when we are editing in a YAML checking editor.
Things we should do in the container build:
Also it occurs to me that
ec ioc validate
for checking ioc instance yaml is woefully inadequate. At present it gets a container with a schema checker in it.It would be far more instructive to instead fetch the generic IOC container it refers to and check it can generate the runtime assets inside of that - and launch the binary. That would pick up all possible errors that can occur. Including those that are currently missing.
This issue supersedes #170 so will be closing that.
The text was updated successfully, but these errors were encountered: