Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Limit the target_app setting to serverless deployments #157042

Closed
weltenwort opened this issue May 8, 2023 · 1 comment · Fixed by #158649
Closed

Limit the target_app setting to serverless deployments #157042

weltenwort opened this issue May 8, 2023 · 1 comment · Fixed by #158649
Assignees
Labels
Feature:Logs UI Logs UI feature Team:Infra Monitoring UI - DEPRECATED DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services

Comments

@weltenwort
Copy link
Member

📓 Summary

With #154145 we introduced the setting xpack.infra.logs.app_target to the infra plugin's config schema. Now that #156837 is available we should limit it to the serverless deployment type so it's not abused in other deployment scenarios.

✔️ Acceptance criteria

@botelastic botelastic bot added the needs-team Issues missing a team label label May 8, 2023
@jsanz jsanz added the Team:Infra Monitoring UI - DEPRECATED DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services label May 16, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI)

@botelastic botelastic bot removed the needs-team Issues missing a team label label May 16, 2023
@weltenwort weltenwort added the Feature:Logs UI Logs UI feature label May 26, 2023
@tonyghiani tonyghiani self-assigned this May 30, 2023
tonyghiani added a commit that referenced this issue May 31, 2023
## 📓 Summary

Closes #157042 

After the implementation of
#156837, we are now able to limit
the `logs.app_target` configuration to be accepted only in a serverless
environment, otherwise, it'll not be accepted.

Since we still need to use a default fallback value for the logs UI app,
the fallback will be applied internally when looking for this config, to
keep the original behaviour unchanged.

## 🧪 Testing

### Serverless environment
- Start Elasticsearch with `yarn es snapshot` and Kibana with `yarn
serverless-oblt`
- Verify that when navigating to Logs pages through the sidebar links or
directly accessing the url `/app/logs` it redirects to discover.

### Normal environment
- Start Elasticsearch with `yarn es snapshot` and Kibana with `yarn
start`
- Verify that when navigating to Logs pages through the sidebar links or
directly accessing the url `/app/logs` the log stream is rendered
correctly.

### Limited to serverless env
To verify that the configuration is only accepted under a serverless
context, set into your kibana.yml or `kibana.dev.yml` the configuration
```yml
xpack.infra.logs.app_target: discover
```
and verify that it triggers a validation error when running Kibana.

---------

Co-authored-by: Marco Antonio Ghiani <[email protected]>
Co-authored-by: Kibana Machine <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Logs UI Logs UI feature Team:Infra Monitoring UI - DEPRECATED DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants