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.

Sign up for GitHub

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

Jump to bottom

✨ Add client gc_max_allocs param #169

Merged
merged 1 commit into from
Jan 11, 2024
Merged

✨ Add client gc_max_allocs param #169

merged 1 commit into from
Jan 11, 2024

Conversation

fairglen
Copy link
Contributor

✨ Add client gc_max_allocs param

  • 🎯 Main theme: Adding support for client gc_max_allocs param
  • 📌 Type of PR: Enhancement
  • 🧪 Relevant tests added: No
  • 🔒 Security concerns: No, this PR does not introduce any obvious security concerns. It's a configuration enhancement and doesn't involve any sensitive data handling or risky operations.

@beechesII
Copy link
Collaborator

@fairglen thank you for your PR. I added molecule tests to ansible-community/ansible-nomad:master. Please update your feature branch with current master.

@beechesII beechesII merged commit c75c802 into ansible-community:master Jan 11, 2024
13 of 14 checks passed
Rendanic pushed a commit to opitzconsulting/ansible-nomad that referenced this pull request Apr 3, 2024
@fairglen @Rendanic
✨ Add client gc_max_allocs param (ansible-community#169)
75c38e8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@RCM7 RCM7 RCM7 approved these changes

Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@fairglen @beechesII @RCM7