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

refactor fleet mode detection and storage #40667

Merged
merged 2 commits into from
Sep 4, 2024

Conversation

leehinman
Copy link
Contributor

Proposed commit message

refactor fleet mode detection and storage

Currently the fleet mode is only detected by looking at the command
line flags. This refactor keeps that behavior but also adds the
ability to set the value based independently. This is important if
you were to embed a Beat within elastic-agent and have it behave as
fleet managed.

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.

Disruptive User Impact

There should be no user observed change.

Author's Checklist

  • [ ]

How to test this PR locally

  • run elastic-agent test suite with agentbeat built from this patch.

Related issues

Use cases

Screenshots

Logs

@leehinman leehinman requested a review from a team as a code owner August 30, 2024 19:42
@leehinman leehinman requested review from faec and VihasMakwana August 30, 2024 19:42
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Aug 30, 2024
Copy link
Contributor

mergify bot commented Aug 30, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @leehinman? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

@leehinman leehinman added backport-skip Skip notification from the automated backport with mergify Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team labels Aug 30, 2024
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Aug 30, 2024
@leehinman leehinman force-pushed the refactor_fleet_mode_detection branch from 3a18c3c to f846c31 Compare September 3, 2024 13:33
@leehinman leehinman merged commit 3309620 into elastic:main Sep 4, 2024
122 checks passed
leehinman added a commit that referenced this pull request Oct 7, 2024
jlind23 pushed a commit that referenced this pull request Oct 7, 2024
* Revert "refactor fleet mode detection and storage (#40667)"

This reverts commit 3309620.

* fix import
mergify bot pushed a commit that referenced this pull request Oct 7, 2024
* Revert "refactor fleet mode detection and storage (#40667)"

This reverts commit 3309620.

* fix import

(cherry picked from commit 60bdc6a)
leehinman added a commit that referenced this pull request Oct 7, 2024
* Revert "refactor fleet mode detection and storage (#40667)"

This reverts commit 3309620.

* fix import

(cherry picked from commit 60bdc6a)

Co-authored-by: Lee E Hinman <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-skip Skip notification from the automated backport with mergify Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants