[Phase 1] Remove Monitoring Console from AWS appframework tests#1866
Draft
gabrielm-splunk wants to merge 1 commit intodevelopfrom
Draft
[Phase 1] Remove Monitoring Console from AWS appframework tests#1866gabrielm-splunk wants to merge 1 commit intodevelopfrom
gabrielm-splunk wants to merge 1 commit intodevelopfrom
Conversation
Remove unnecessary MC deployments from AWS appframework test suites to reduce test execution time and resource overhead. Changes: - Remove MC from S1 tests (standalone): 2 test files, ~300 lines - Remove MC from M4 tests (multisite): 2 test files, ~345 lines - Remove MC from C3 tests (cluster): 2 test files, ~473 lines Technical details: - Removed MC S3 uploads, specs, and deployment calls - Removed MonitoringConsoleRef from CR specs - Removed MC verification calls - Updated app source info arrays to exclude MC - All files compile successfully Total: ~946 net lines removed across 5 test files Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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
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.
Summary
Remove unnecessary Monitoring Console deployments from AWS appframework tests to reduce test execution time and resource overhead.
Motivation
The Monitoring Console (MC) is deployed in every AWS appframework test but adds significant overhead without providing proportional testing value:
Removing MC from these tests will:
Changes
Files Modified (5 total, ~946 net lines removed)
S1 Tests (Standalone):
test/appframework_aws/s1/appframework_aws_test.go- ~266 lines removedM4 Tests (Multisite):
test/appframework_aws/m4/appframework_aws_test.go- ~141 lines removedtest/appframework_aws/m4/manager_appframework_test.go- ~172 lines removedC3 Tests (Cluster):
test/appframework_aws/c3/appframework_aws_test.go- ~194 lines removedtest/appframework_aws/c3/manager_appframework_test.go- ~260 lines removedTechnical Changes
For each test file:
MonitoringConsoleReffrom CR specs (Standalone, ClusterManager, SearchHeadCluster)VerifyMonitoringConsoleReady)allAppSourceInfoarrays to exclude MC entriesVerification
✅ All 5 modified files compile successfully:
ginkgo build ./appframework_aws/s1/ ./appframework_aws/m4/ ./appframework_aws/c3/ # All tests compile without errors✅ Single commit on branch
remove-mc-aws-phase1✅ ~946 net lines removed (1032 deletions, 86 additions)
✅ No functional changes to CR deployment or app framework testing
Testing
Next Steps
Checklist
🤖 Generated with Claude Code