Update README files using the url placeholder for elastic documentation links#4068
Update README files using the url placeholder for elastic documentation links#4068mrodm merged 9 commits intoelastic:mainfrom
Conversation
💔 Build Failed
Expand to view the summary
Build stats
Test stats 🧪
Steps errors
Expand to view the steps failures
|
🌐 Coverage report
|
e08d5bb to
3c20e06
Compare
3e2a7a6 to
8a5a1dc
Compare
f0c51fe to
351682c
Compare
| // Elastic package links definitions | ||
| ELASTIC_PACKAGE_LINKS_FILE_PATH = "${env.HOME}/${env.BASE_DIR}/links_table.yml" | ||
|
|
There was a problem hiding this comment.
By default, elastic-package would use the file at the root of the directory. But, I would prefer to keep it explicitly this path.
efd6
left a comment
There was a problem hiding this comment.
Approving for the SEI-owned files.
Is there testing in elastic-package for use of links that are included in the links_table.yml file to prevent them flowing back in to markdown files?
zmoog
left a comment
There was a problem hiding this comment.
LGTM, from cloud monitoring.
crespocarlos
left a comment
There was a problem hiding this comment.
LGTM! from Infra Monitoring UI. Tested it following the test steps successfully. elastic-package 0.61 still doesn't support this.
Still not released a new version with these changes. This will be included in the next one (0.62.0) |
For the time being, there is no validation rule in place to check this. Depending on how this evolves, it could be added later a check to enforce the usage of links present in that file. |
alvarezmelissa87
left a comment
There was a problem hiding this comment.
Code LGTM for the ML packages (DGA, Problem child) ⚡
What does this PR do?
Update README files to use the new
{{ url <key> <link> }}notation introduced in elastic/elastic-package#938To accomplish that, a new file in the root of the repository
links_table.ymlhas been added with all the links to elastic documentation found in the current packages.In general, there are no changes in README contents with this PR. There are some changes due to some markdown syntax issues.
Checklist
[ ] I have verified that all data streams collect metrics or logs.[ ] I have added an entry to my package'schangelog.ymlfile.[ ] I have verified that Kibana version constraints are current according to guidelines.How to test this PR locally
make build)elastic-package build. This command should generate the README without failures.Author's Checklist
Related issues