Pinging @elastic/ingest-management (Team:Ingest Management)

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: afa472e

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

Distributable file count

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

Hi @nchaulet

Today, we performing testing around enrollment token keys on 7.11 BC2 Kibana cloud build. Build details are as follows:

BUILD 37605
COMMIT a5126f7a280a6f4a27dc3aca65c1c89ccd1ac694

We have observed that when a token is deleted for active policy and no new token is generated for that policy, then enrollment token field is populated with default policy's token that was available in active state in agent enrollment flyout. Also, we were successfully able to install agent used that updated command.

However, no validation message such as 'no active keys available for this policy' was shown to agent on selecting policy with no active enrollment token on agent enrollment flyout.

Though, enrollment field was displayed blank under Authentication settings on agent enrollment flyout.

Please let us know if anything is required from our side.

Screenshot: