Use an empty config file to produce docs #6092
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tracking issue
NA
Why are the changes needed?
After #5972 we require a config file in order to run the
docs
subcommand in all components.We use the
docs
subcommand to produce the rst files under thedocs
directory, e.g. https://github.com/flyteorg/flyte/blob/master/docs/deployment/configuration/generated/flyteadmin_config.rst.What changes were proposed in this pull request?
This PR introduces an empty config file to be passed to each of the invocations of the components
docs
subcommands in https://github.com/flyteorg/flyte/blob/master/script/generate_config_docs.sh#L46-L49.How was this patch tested?
Ran
make release_automation
locally and confirmed that the command succeeds and docs are generated.Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link