-
Notifications
You must be signed in to change notification settings - Fork 71
Bugfix/10.5.20/update agent hostname #1017
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…s. Reformat agent update classes and handling exceptions.
…stack/UTMStack into bugfix/10.5.20/update-agent-hostname
…/update-agent-hostname
…name' into bugfix/10.5.20/update-agent-hostname
…name' into bugfix/10.5.20/update-agent-hostname
c3s4rfred
approved these changes
Feb 12, 2025
c3s4rfred
approved these changes
Feb 12, 2025
dayat81
pushed a commit
to dayat81/utmstack
that referenced
this pull request
Aug 9, 2025
* Allow hostname and ip change in agent machines * Updating agent.proto and rebuild classes. Upgrading liquibase and protobuf versions * feat: update compliance reports data * Adding update agent attributes services, vms and other used classes * fix: prevent deletion of system-owned dashboards and visualizations * feat: show lock icon for private IP addresses instead of country flag * Fixing pom.xml error with protoc version and regenerating grpc classes. Reformat agent update classes and handling exceptions. * Adding documentation to the POST method used to update agent's attributes. * Removing unused condition. * fix tls insecure connection between agent and master * feat: set ip address to agent * chore: enable creation of new alert when a datasource is down * chore: enable creation of new alert when a datasource is down --------- Co-authored-by: Yorjander Hernandez Vergara <[email protected]> Co-authored-by: Freddy R. Laffita Almaguer <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.