Updates the init-config target to validate the passed --git-ref is actually the one that is checked out.

docs-builder assembler config init --git-ref 2c41839a928e4fbb1f838ec46a05c81cbe346144

If you just want the latest/edge you can omit --git-ref

docs-builder assembler config init

Then you can force remote as a configuration source.

docs-builder assembler clone --config-source remote
docs-builder assembler build -c remote

--config-source and -c can be used interchangeably.

If the application folder docs-builder assembler config init writes to is not available both of these will exit with an error code.

Every invocation of docs-builder and docs-assembler will indicate what config source is being used:

info ::e.d.c.tionFileProvider:: ConfigurationSource.Remote: git ref '2c41839a928e4fbb1f838ec46a05c81cbe346144', in /Users/mpdreamz/Library/Application Support/elastic/docs-builder/config-clone/config

Defaults if none are provided

If --config-source is not provided it will default to ConfigurationSource.Local if config exists in the pwd, this is the default during development.

Otherwise ConfigurationSource.Embedded will use the configuration files embedded in the binary.

Create assembler workspaces

In an empty folder you can config init --local to clone the repository to the current working directory (pwd) instead. This makes it a lot easier to create a local assemble workspace to validate changes.

docs-builder assembler config init --local
docs-builder assembler clone -c local # (-c 'local' is default and can be omitted) 
docs-builder assembler build -c local # (-c 'local' is default and can be omitted) 

In a follow up we will add commands to build to pick up different checkouts more easily.