Add auto generation support for content package readme generation

[ishleenk17]

Issue: #3476

Related Issue: https://github.com/elastic/obs-integration-team/issues/1004

[teresaromero]

i don't think the ci failure is related to this change. perhaps the base branch is outdated? we fixed recently the zipkin errors... could you update the branch and check tests pass?

other than that i dont see any blocker for this, unless the fact that we need 3.6.1 package-spec bumped into elastic-package for this change? WDYT cc @mrodm

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: acebd18

Failed CI Steps

• :go: Integration test: auditd_manager

History

• 💔 Build #7759 failed 7803d48

[mrodm]

other than that i dont see any blocker for this, unless the fact that we need 3.6.1 package-spec bumped into elastic-package for this change? WDYT cc @mrodm

LGTM. As you mentioned, a new package-spec release should be updated in elastic-package (containing elastic/package-spec#1144) in order to be able to use the folder _dev/build/docs. Until that happens, any content package adding _dev/build/docs folder will fail when running elastic-package check command.

[ishleenk17]

other than that i dont see any blocker for this, unless the fact that we need 3.6.1 package-spec bumped into elastic-package for this change? WDYT cc @mrodm

LGTM. As you mentioned, a new package-spec release should be updated in elastic-package (containing elastic/package-spec#1144) in order to be able to use the folder _dev/build/docs. Until that happens, any content package adding _dev/build/docs folder will fail when running elastic-package check command.

@mrodm
For now we don't have any package using autogeneration yet. So , IMO we should be good to merge this.
Once the new version of elastic-package is released I will update my team to use it.