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

Cherry-pick #18232 to 7.x: Fix default configuration after enroll #18238

Merged
merged 1 commit into from
May 5, 2020

Conversation

michalpristas
Copy link
Contributor

Cherry-pick of PR #18232 to 7.x branch. Original message:

What does this PR do?

Changes default configuration after enroll so agent is not in standalone mode

Why is it important?

To switch behavior from standalone to enroll

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

cc @ruflin @ph

@michalpristas michalpristas added bug backport Project:fleet Ingest Management:alpha1 Group issues for ingest management alpha1 labels May 5, 2020
@michalpristas michalpristas self-assigned this May 5, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ingest-management (Project:fleet)

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label May 5, 2020
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

Pipeline View Test View Changes Artifacts preview stats

Expand to view the summary

Build stats

@michalpristas michalpristas merged commit 38b2ee8 into elastic:7.x May 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport bug Ingest Management:alpha1 Group issues for ingest management alpha1 needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants