Skip to content

BB-694: Update auth config schema #2659

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

Open
wants to merge 2 commits into
base: development/9.0
Choose a base branch
from

Conversation

tmacro
Copy link
Contributor

@tmacro tmacro commented Jul 15, 2025

Extends the existing schema to support basic auth and stricter checking of kerberos.

@bert-e
Copy link
Contributor

bert-e commented Jul 15, 2025

Hello tmacro,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval
/bypass_build_status Bypass the build and test status
/bypass_commit_size Bypass the check on the size of the changeset TBA
/bypass_incompatible_branch Bypass the check on the source branch prefix
/bypass_jira_check Bypass the Jira issue check
/bypass_peer_approval Bypass the pull request peers' approval
/bypass_leader_approval Bypass the pull request leaders' approval
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request TBA
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

@tmacro tmacro force-pushed the improvement/BB-694/update_auth_config_schema branch from 1b5e9f3 to 34a1825 Compare July 15, 2025 15:19
Copy link

codecov bot commented Jul 15, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.65%. Comparing base (57a66a0) to head (34a1825).
Report is 1 commits behind head on development/9.0.

Additional details and impacted files

Impacted file tree graph

Files with missing lines Coverage Δ
...nsions/notification/NotificationConfigValidator.js 100.00% <100.00%> (ø)
...tensions/notification/destination/KafkaProducer.js 100.00% <100.00%> (ø)
extensions/notification/index.js 75.00% <100.00%> (ø)

... and 4 files with indirect coverage changes

Components Coverage Δ
Bucket Notification 76.57% <100.00%> (+0.99%) ⬆️
Core Library 80.30% <ø> (+0.62%) ⬆️
Ingestion 70.14% <ø> (-0.09%) ⬇️
Lifecycle 77.94% <ø> (ø)
Oplog Populator 85.06% <ø> (ø)
Replication 58.55% <ø> (ø)
Bucket Scanner 85.60% <ø> (ø)
@@                 Coverage Diff                 @@
##           development/9.0    #2659      +/-   ##
===================================================
+ Coverage            73.35%   73.65%   +0.30%     
===================================================
  Files                  201      201              
  Lines                13390    13396       +6     
===================================================
+ Hits                  9822     9867      +45     
+ Misses                3558     3519      -39     
  Partials                10       10              
Flag Coverage Δ
api:retry 9.50% <80.00%> (+0.03%) ⬆️
api:routes 9.32% <80.00%> (+0.03%) ⬆️
bucket-scanner 85.60% <ø> (ø)
ft_test:queuepopulator 10.78% <80.00%> (+1.87%) ⬆️
ingestion 12.57% <80.00%> (+0.02%) ⬆️
lib 7.41% <80.00%> (+0.03%) ⬆️
lifecycle 18.80% <80.00%> (+0.02%) ⬆️
notification 1.07% <0.00%> (-0.01%) ⬇️
replication 18.55% <80.00%> (+0.02%) ⬆️
unit 49.07% <100.00%> (+0.06%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@scality scality deleted a comment from bert-e Jul 15, 2025
@bert-e
Copy link
Contributor

bert-e commented Jul 15, 2025

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

@tmacro
Copy link
Contributor Author

tmacro commented Jul 15, 2025

/create_integration_branches

@scality scality deleted a comment from bert-e Jul 15, 2025
@bert-e
Copy link
Contributor

bert-e commented Jul 15, 2025

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

The following options are set: create_integration_branches

@tmacro tmacro changed the title BB-695: Update auth config schema BB-694: Update auth config schema Jul 15, 2025
destinations: [{
const testCases = [
{
valid:false,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
valid:false,
valid: false,

ssl: joi.boolean(),
protocol: joi.string(),
const sslSchema = joi.object({
ssl: joi.boolean().default(false),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would having type: "ssl" be more consistent with the other auth types?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants