Skip to content

[ML] Adds a check if the current user can clone a job. - #27496

Merged
walterra merged 1 commit into
elastic:masterfrom
walterra:ml-job-clone-indexpattern-check
Dec 20, 2018
Merged

walterra merged 1 commit into
elastic:masterfrom
walterra:ml-job-clone-indexpattern-check

Conversation

@walterra

@walterra walterra commented Dec 19, 2018 •

Copy link
Copy Markdown
Contributor

Summary

Fixes #26695.

Adds a check if all index patterns necessary to clone a job are available for the current user. The check will only allow cloning of a job if the user has the right permissions and can still access the indexPattern the job was created for. An indexPattern could either have been deleted since the the job was created or the current user doesn't have the required permissions to access the indexPattern.

The "Clone Job" action in the jobs list action menu will be greyed out and unavailable for that job.

image

Checklist

Use strikethroughs to remove checklist items you don't feel are applicable to this PR.

For maintainers

@walterra walterra added bug Fixes for quality problems that affect the customer experience v7.0.0 :ml Feature:Anomaly Detection ML anomaly detection labels Dec 19, 2018
@walterra walterra self-assigned this Dec 19, 2018
@elasticmachine

Copy link
Copy Markdown
Contributor

Pinging @elastic/ml-ui

@alvarezmelissa87 alvarezmelissa87 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM ⚡️

@elasticmachine

Copy link
Copy Markdown
Contributor

💚 Build Succeeded

@jgowdyelastic jgowdyelastic left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@peteharverson peteharverson left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Whilst the datafeed for a job references the Elasticsearch index(es), with the job wizards and results views relying so heavily on the Kibana index pattern, it makes sense to prevent the user cloning a job if they don't have access to the index pattern either because it's been deleted or it's not available in the current user's Kibana space.

@walterra
walterra merged commit 5a7ab18 into elastic:master Dec 20, 2018
@walterra
walterra deleted the ml-job-clone-indexpattern-check branch December 20, 2018 09:34
walterra added a commit to walterra/kibana that referenced this pull request Dec 20, 2018
…uired to clone a job. (elastic#27496)

Adds a check if all index patterns necessary to clone a job are available for the current user. The check will only allow cloning of a job if the user has the right permissions and can still access the indexPattern the job was created for. An indexPattern could either have been deleted since the the job was created or the current user doesn't have the required permissions to access the indexPattern. The "Clone Job" action in the jobs list action menu will be greyed out and unavailable for that job.
walterra added a commit to walterra/kibana that referenced this pull request Dec 20, 2018
…uired to clone a job. (elastic#27496)

Adds a check if all index patterns necessary to clone a job are available for the current user. The check will only allow cloning of a job if the user has the right permissions and can still access the indexPattern the job was created for. An indexPattern could either have been deleted since the the job was created or the current user doesn't have the required permissions to access the indexPattern. The "Clone Job" action in the jobs list action menu will be greyed out and unavailable for that job.
walterra added a commit that referenced this pull request Dec 21, 2018
…uired to clone a job. (#27496) (#27569)

Adds a check if all index patterns necessary to clone a job are available for the current user. The check will only allow cloning of a job if the user has the right permissions and can still access the indexPattern the job was created for. An indexPattern could either have been deleted since the the job was created or the current user doesn't have the required permissions to access the indexPattern. The "Clone Job" action in the jobs list action menu will be greyed out and unavailable for that job.
walterra added a commit that referenced this pull request Dec 21, 2018
…uired to clone a job. (#27496) (#27568)

Adds a check if all index patterns necessary to clone a job are available for the current user. The check will only allow cloning of a job if the user has the right permissions and can still access the indexPattern the job was created for. An indexPattern could either have been deleted since the the job was created or the current user doesn't have the required permissions to access the indexPattern. The "Clone Job" action in the jobs list action menu will be greyed out and unavailable for that job.
patrykkopycinski pushed a commit to patrykkopycinski/kibana that referenced this pull request May 6, 2026
…uired to clone a job. (elastic#27496)

Adds a check if all index patterns necessary to clone a job are available for the current user. The check will only allow cloning of a job if the user has the right permissions and can still access the indexPattern the job was created for. An indexPattern could either have been deleted since the the job was created or the current user doesn't have the required permissions to access the indexPattern. The "Clone Job" action in the jobs list action menu will be greyed out and unavailable for that job.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Fixes for quality problems that affect the customer experience Feature:Anomaly Detection ML anomaly detection :ml release_note:fix v6.6.0 v6.7.0 v7.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants