Skip to content
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

feature/per tenant settings #2790

Merged
merged 5 commits into from
Feb 17, 2024

Conversation

amanji
Copy link
Contributor

@amanji amanji commented Feb 16, 2024

  • Adds --emit-did-peer-{2 | 4} per tenant setting
  • Adds --preserve-exchange-records per tenant setting
  • Adds --requests-through-public-did per tenant setting

Resolves: #2724
Resolves: #2648
Resolves: #2572

Signed-off-by: Akiff Manji <amanji@petridish.dev>
Signed-off-by: Akiff Manji <amanji@petridish.dev>
Signed-off-by: Akiff Manji <amanji@petridish.dev>
@amanji amanji marked this pull request as ready for review February 16, 2024 17:13
@swcurran
Copy link
Member

Did any other work get done on this that would be worth documenting? Other than simply adding the lines, was anything else done that might help future per tenant setting additions?

@loneil — does simply adding these items result in them being exposed/updateable in Traction, or is there another PR needed there to add these three settings to expose them in the Traction UI?

Thanks!

@loneil
Copy link
Contributor

loneil commented Feb 16, 2024

They will need a UI addition to add the fields on the settings page is all

@amanji
Copy link
Contributor Author

amanji commented Feb 16, 2024

Should I do a quick PR to add them in Traction?

@amanji
Copy link
Contributor Author

amanji commented Feb 16, 2024

Did any other work get done on this that would be worth documenting? Other than simply adding the lines, was anything else done that might help future per tenant setting additions?

@loneil — does simply adding these items result in them being exposed/updateable in Traction, or is there another PR needed there to add these three settings to expose them in the Traction UI?

Thanks!

Not for this PR. It would be worthwhile exploring refactoring code to wholesale include parameters and create an exclusion list for those that shouldn't be tenant specific. I'd argue that a refactor of the argparse file should be explored to come up with consistent parameter names, etc.

@loneil
Copy link
Contributor

loneil commented Feb 16, 2024

Should I do a quick PR to add them in Traction?

This would be in an RC right? Maybe would have to just wait until the release that includes it is rolled out anyways?

@jamshale
Copy link
Contributor

The failing integration test seems to be a fragile test. The same test failed for my recent draft PR.

@amanji
Copy link
Contributor Author

amanji commented Feb 16, 2024

Should I do a quick PR to add them in Traction?

This would be in an RC right? Maybe would have to just wait until the release that includes it is rolled out anyways?

Yeah we can file an issue for now and I'll add it as soon as a new version is released

Copy link

sonarcloud bot commented Feb 16, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@swcurran swcurran merged commit a36094e into hyperledger:main Feb 17, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants