-
Notifications
You must be signed in to change notification settings - Fork 111
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
Bug-Automate Manger gets linked to max 100 Node IDs#5631 #5761
Conversation
👷 Deploy Preview for chef-automate processing. 🔨 Explore the source changes: e778315 🔍 Inspect the deploy log: https://app.netlify.com/sites/chef-automate/deploys/6149fc471a5a0f00070dba62 |
Signed-off-by: Shivangi Singh <shisingh@progress.com>
Signed-off-by: Shivangi Singh <shisingh@progress.com>
Signed-off-by: Shivangi Singh <shisingh@progress.com>
e367317
to
cc18f57
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Working fine, thanks
Signed-off-by: Shivangi Singh <shisingh@progress.com>
Kudos, SonarCloud Quality Gate passed!
|
🔩 Description: What code changed, and why?
⛓️ Related Resources
Node manager service, default Automate Manger gets linked to max 100 Node IDs #5761
👍 Definition of Done
More than 100 nodes linked to automate manager.
👟 How to Build and Test the Change
✅ Checklist
All PRs must tick these:
With occasional exceptions, all PRs from Progress employees must tick these:
make spell
in any component directory)All PRs from Progress employees should tick these if appropriate:
Please add a note next to any checkbox above if you are NOT ticking it.
📷 Screenshots, if applicable