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

[FTR] update svl search config and custom role test #196126

Merged
merged 3 commits into from
Oct 14, 2024

Conversation

dmlemeshko
Copy link
Member

@dmlemeshko dmlemeshko commented Oct 14, 2024

Summary

This PR removes xpack.cloud.serverless.project_type from FTR config, the value breaks mockIdpPlugin that expects it to be defined as search. We will address project type unification separately.

Closes #195976

@dmlemeshko dmlemeshko self-assigned this Oct 14, 2024
@dmlemeshko dmlemeshko added release_note:skip Skip the PR/issue when compiling release notes v9.0.0 FTR labels Oct 14, 2024
@dmlemeshko dmlemeshko requested a review from pheyos October 14, 2024 12:31
Comment on lines 22 to 27
`--xpack.cloud.id=ES3_FTR_TESTS:ZmFrZS1kb21haW4uY2xkLmVsc3RjLmNvJGZha2Vwcm9qZWN0aWQuZXMkZmFrZXByb2plY3RpZC5rYg==`,
`--xpack.cloud.serverless.project_id=fakeprojectid`,
`--xpack.cloud.serverless.project_name=ES3_FTR_TESTS`,
`--xpack.cloud.serverless.project_type=elasticsearch`,
`--xpack.cloud.base_url=https://fake-cloud.elastic.co`,
`--xpack.cloud.profile_url=/user/settings/`,
`--xpack.cloud.billing_url=/billing/overview/`,
Copy link
Member Author

Choose a reason for hiding this comment

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

@pheyos we probably need to move these arguments to shared config as it is relevant for all projects. But I'm not sure if we want to generate id/name of have a static value based on project type.

Comment on lines +65 to +66
// Playground should be also hidden, probably a bug
// await testSubjects.missingOrFail('~nav-item-id-searchPlayground');
Copy link
Member Author

@dmlemeshko dmlemeshko Oct 14, 2024

Choose a reason for hiding this comment

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

@elastic/search-kibana

It seems like application privileges are not properly applied to searchPlayground. The role I defined has only access to Discover, but I still see and able to open Playground link, later to see error message

Screenshot 2024-10-14 at 13 34 41

Similar question is if Connectors should be visible by default?

Role descriptors:

{
        elasticsearch: {
          indices: [{ names: ['logstash-*'], privileges: ['read', 'view_index_metadata'] }],
        },
        kibana: [
          {
            feature: {
              discover: ['read'],
            },
            spaces: ['*'],
          },
        ],
      }

Copy link
Contributor

@TattdCodeMonkey TattdCodeMonkey Oct 14, 2024

Choose a reason for hiding this comment

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

Yes, this is known and something that is being worked on currently

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

cc @dmlemeshko

@dmlemeshko dmlemeshko marked this pull request as ready for review October 14, 2024 16:09
@dmlemeshko dmlemeshko requested a review from a team as a code owner October 14, 2024 16:09
@dmlemeshko dmlemeshko added the backport:skip This commit does not require backporting label Oct 14, 2024
@dmlemeshko dmlemeshko merged commit 41850b6 into elastic:main Oct 14, 2024
34 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting FTR release_note:skip Skip the PR/issue when compiling release notes v9.0.0
Projects
None yet
3 participants