mcarroll1 opened a new pull request, #744: URL: https://github.com/apache/solr-operator/pull/744
- Added `Ovewrite` flag (defaults to false). If flag is true, setup-zk initContainer will check applied security.json against version in the secret and apply if there is a diff - Updated descriptions about `maxPodsUnavailable`, as negative numbers don't appear to be work - Was running into issues with `GINGKO_PARAMS` when running integration tests, so added a default I've updated the integration test for applying/updating security.json. I have this to the point that the feature is working via the test. However, I don't see an easy way to actually test the updated auth. My test attempts to adding a permission statement to the update handler and then force an HTTP 401. I've created a separate curl pod to handle this. However, I'm having trouble getting that curl to work. It took a lot of effort to get to this point in the test. Any advice here would be greatly appreciated. This feature is important to the CI for my team, hence me adding two features around security.json in short order. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
