-
Notifications
You must be signed in to change notification settings - Fork 251
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
feat: add connector BOM modules #4533
feat: add connector BOM modules #4533
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could them be already used in the system-tests
runtimes where possible?
Co-authored-by: andrea bertagnolli <[email protected]>
I haven't looked at that yet, but it would definitely make sense. [edit] a first rough attempt at using the BOMs showed that this might be a bit more involved than anticipated, because our test runtimes sometimes leave out extensions that they don't need. So if we want to use BOMs in testing (of which I'm not 100% convinced, TBH) then I suggest we do this in another PR. WDYT? |
eb8e6cf
to
4b25372
Compare
4b25372
to
38cfeab
Compare
extensions/common/iam/identity-trust/identity-trust-sts/build.gradle.kts
Outdated
Show resolved
Hide resolved
3776492
to
13b0caa
Compare
13b0caa
to
ac314e3
Compare
a9f03f2
to
83fba74
Compare
What this PR changes/adds
Adds Bill-of-Material (BOM) modules
Why it does that
to make the life of everyone who aims at creating their own connector runtime much easier.
Further notes
example.properties
, which contains dummy config values. this is used for testingsmoke-test the BOMspublish the BOMs' autodoc manifest is also still missing -> subsequent PRLinked Issue(s)
Closes # <-- insert Issue number if one exists
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.