elastic / elastic/fleet-server

Add integration tests for permission output changes

Open
#456 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
113
Forks
117
Avg merge
1d 16h
Merged PRs (30d)
112

Description

Adding integration tests for the permission output changes should be done to provide better coverage of that code path. At the moment it is partially tested, but not the whole flow.

The following flow is a good start at a test:

* Enroll a fake Agent into a policy
* Add new revision of the policy adjust the permissions
* Verify that when the fake Agent checks-in (and when its already connected) it gets pushed the new policy with an newly created API key with the correct permission.

The inverse would also be good to add (adjusting the policy without touching the permissions) and see that a new API key is not created.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.