**What this PR does / why we need it**:
Update doc generator tool to validate if slice element is a root block.
Add missing `period_config` root block to doc generator tool.
**Special notes for your reviewer**:
**Checklist**
- [ ] Documentation updated
The `period_config` block configures what index schemas should be used for from specific time periods.
```yaml
# The date of the first day that index buckets should be created. Use a date in
# the past if this is your only period_config, otherwise use a date when you
# want the schema to switch over. In YYYY-MM-DD format, for example: 2018-04-15.
[from: <daytime>]
# store and object_store below affect which <storage_config> key is used.
# Which store to use for the index. Either aws, aws-dynamo, gcp, bigtable,
# bigtable-hashed, cassandra, boltdb or boltdb-shipper.
[store: <string> | default = ""]
# Which store to use for the chunks. Either aws, azure, gcp, bigtable, gcs,
# cassandra, swift or filesystem. If omitted, defaults to the same value as
# store.
[object_store: <string> | default = ""]
# The schema version to use, current recommended schema is v11.
[schema: <string> | default = ""]
# Configures how the index is updated and stored.
index:
# Table prefix for all period tables.
[prefix: <string> | default = ""]
# Table period.
[period: <duration>]
# A map to be added to all managed tables.
[tags: <mapofstringtostring>]
# Configured how the chunks are updated and stored.
chunks:
# Table prefix for all period tables.
[prefix: <string> | default = ""]
# Table period.
[period: <duration>]
# A map to be added to all managed tables.
[tags: <mapofstringtostring>]
# How many shards will be created. Only used if schema is v10 or greater.
[row_shards: <int>]
```
### azure_storage_config
### azure_storage_config
The `azure_storage_config` block configures the connection to Azure object storage backend. The supported CLI flags `<prefix>` used to reference this configuration block are:
The `azure_storage_config` block configures the connection to Azure object storage backend. The supported CLI flags `<prefix>` used to reference this configuration block are:
FromDayTime`yaml:"from" doc:"description=The date of the first day that index buckets should be created. Use a date in the past if this is your only period_config, otherwise use a date when you want the schema to switch over. In YYYY-MM-DD format, for example: 2018-04-15."`
FromDayTime`yaml:"from" doc:"description=The date of the first day that index buckets should be created. Use a date in the past if this is your only period_config, otherwise use a date when you want the schema to switch over. In YYYY-MM-DD format, for example: 2018-04-15."`
// type of index client to use.
// type of index client to use.
IndexTypestring`yaml:"store"`
IndexTypestring`yaml:"store" doc:"description=store and object_store below affect which <storage_config> key is used.\nWhich store to use for the index. Either aws, aws-dynamo, gcp, bigtable, bigtable-hashed, cassandra, boltdb or boltdb-shipper. "`
// type of object client to use; if omitted, defaults to store.
// type of object client to use; if omitted, defaults to store.
ObjectTypestring`yaml:"object_store"`
ObjectTypestring`yaml:"object_store" doc:"description=Which store to use for the chunks. Either aws, azure, gcp, bigtable, gcs, cassandra, swift or filesystem. If omitted, defaults to the same value as store."`
Schemastring`yaml:"schema"`
Schemastring`yaml:"schema" doc:"description=The schema version to use, current recommended schema is v11."`
IndexTablesPeriodicTableConfig`yaml:"index"`
IndexTablesPeriodicTableConfig`yaml:"index" doc:"description=Configures how the index is updated and stored."`
ChunkTablesPeriodicTableConfig`yaml:"chunks"`
ChunkTablesPeriodicTableConfig`yaml:"chunks" doc:"description=Configured how the chunks are updated and stored."`
RowShardsuint32`yaml:"row_shards"`
RowShardsuint32`yaml:"row_shards" doc:"description=How many shards will be created. Only used if schema is v10 or greater."`
// Integer representation of schema used for hot path calculation. Populated on unmarshaling.
// Integer representation of schema used for hot path calculation. Populated on unmarshaling.