## Summary
We're moving to a different vault address/instance when we're on the
elastic-wide buildkite infra. While the migration is in progress, we can
bridge between using this solution.
✅ Tested the status quo by running the PR pipeline (tests all the loads
from `pre-command`) and by using `ci:cloud-deploy` (tests vault
writing).
🟠 Tested the new vault provider on this PR:
https://github.com/elastic/kibana/pull/171317
The secrets can be accessed, *but they can't be written* (neither by me
nor) by the PR pipeline. Change requested here:
https://elasticco.atlassian.net/browse/ENGPRD-414
However, this PR can be merged without figuring out write access to
secrets, this will work as long as we're on the `kibana-buildkite`
infra.
---
Closes: https://github.com/elastic/kibana-operations/issues/28
Based on: https://github.com/elastic/kibana/pull/157220
---------
Co-authored-by: Jon <jon@budzenski.me>
## Summary
Closes#160803
This PR removes the `CI Composite` story because it has been broken
since at least ac23dce29f (and possibly
since b862a6c181). The functionality is
covered by the generated `index.html` in
dda4498fee/.buildkite/scripts/steps/storybooks/build_and_upload.ts (L105-L120)
To fix the composite story requires generating `stories.json` for every
storybook, which requires migrating the repo off the deprecated
`storiesOf` API. That task is quite extensive and would be better
handled alongside an upgrade to Storybook 7.x
## Summary
Bumps node.js to 18.17.0 (replacement for PR #144012 which was later
reverted)
As a result, these categorical additions were needed:
- `node` evocations will need the `--openssl-legacy-provider` flag,
wherever it would use certain crypto functionalities
- tests required updating of the expected HTTPS Agent call arguments,
`noDelay` seems to be a default
- `window.[NAME]` fields cannot be written directly
- some stricter typechecks
This is using our in-house built node.js 18 versions through the URLs
the proxy-cache. (built with
https://github.com/elastic/kibana-custom-nodejs-builds/pull/4)
These urls are served from a bucket, where the RHEL7/Centos7 compatible
node distributables are. (see:
https://github.com/elastic/kibana-ci-proxy-cache/pull/7)
Further todos:
- [x] check docs wording and consistency
- [ ] update the dependency report
- [x] explain custom builds in documentation
- [x] node_sass prebuilts
---------
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Tiago Costa <tiago.costa@elastic.co>
Co-authored-by: Thomas Watson <w@tson.dk>
* [QA][Code Coverage] Drop dead code
We've some code no longer used,
that was used when code coverage was
orchestrated in Jenkins.
Since we use Buildkite instead,
we can drop this code.
* Updated the docs to reflect we
no longer use Jenkins and use
Buildkite instead.
* Updated doc per review and dropped the bit about 4 indexes,
since we no longer need the other R & D job.
* built control group embeddable featuring inline control creation and editing, and DndKit based drag and drop.
Co-authored-by: andreadelrio <delrio.andre@gmail.com>
