Testing K2 Integration #820
Conversation
…ity.enable flag on startup
…bda which would fetch transaction_id on run
1. Changes to start security module even before the agent is activated, thus, init on active_agent callback have been removed and instead added along with module load phase. 2. Updated agent refresh with policy and linking metadata along with agent config for security module 3. Removed deprecated security module configs constomer_id and accessor_token
…config' into k2_integration
…nstead of NRSecurityAgentConfig for generating a config.
🦙 MegaLinter status: ❌ ERROR
See detailed report in MegaLinter reports MegaLinter is graciously provided by |
Codecov Report
@@ Coverage Diff @@
## develop-k2-integration #820 +/- ##
==========================================================
- Coverage 76.40% 73.24% -3.17%
==========================================================
Files 198 198
Lines 19327 19369 +42
Branches 3307 3308 +1
==========================================================
- Hits 14766 14186 -580
- Misses 3716 4268 +552
- Partials 845 915 +70
... and 57 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Before contributing, please read our contributing guidelines and code of conduct.
Overview
Describe the changes present in the pull request
Related Github Issue
Include a link to the related GitHub issue, if applicable
Testing
The agent includes a suite of tests which should be used to
verify your changes don't break existing functionality. These tests will run with
Github Actions when a pull request is made. More details on running the tests locally can be found
here,
For most contributions it is strongly recommended to add additional tests which
exercise your changes.