rgardler-msft
rgardler-msft
Currently we test for success of a command using ``. This allows us to fuzzy match almost any output. This is quick to create since the author need only paste...
In order to work with the CLI past deployment we need to be able to work with the environment variables. In order to lookup items in the portal we need...
As can be seen in [this PR discussion](https://github.com/Azure/InnovationEngine/pull/6#pullrequestreview-1293866623) there is an INCLUDE mechanism in the docs publishing flow. At present Innovation Engine simply ignores these lines. Is this acceptable? Do...
Currently test mode will continue past the first failure, sometimes this is useful but the majority of the time it would be better to fail fast. Default behaviour should be...
Currently output is hard to read as it is essentially a wall of text. Here are some things we could do to make it more readable in interactive mode: -...
It seems that IE can't currently execute background processes. This means that some scripts are not possible, for example, I'm trying to write a doc that will create and deploy...
We can now add Copilot to an issue and it execute the tasks identified. When it has completed it submits a PR for review. Perhaps the easiest way to review...
Currently when an exec doc causes an error there is nothing in syserror. Output contains the entire output of the run, including things that ran successfully. This would allow for...
Currently, in interactive mode, the user is presented with the content ahead of the next command block, it then pauses, waiting for the user to execute the command. Once executed...
At Ignite and other events we have presented the vision of Innovation Engine alongside powerful AI assisted authoring tools. This video should be linked from the README of Innovation Engine.