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

Full support of aws-secret-manager #6953

Conversation

JiriOndrusek
Copy link
Contributor

fixes #6673, #6952

Aws-secret-manager native profile is added.
Tests are moved into aws2-groupped module.
Test coverage is extended to cover credentialsProvider and missing headers.

@JiriOndrusek JiriOndrusek force-pushed the full-support-aws-secret-manager-plus-native branch 2 times, most recently from 46100c6 to 16fa3de Compare January 29, 2025 13:35
@JiriOndrusek JiriOndrusek marked this pull request as draft January 29, 2025 13:46
@JiriOndrusek JiriOndrusek force-pushed the full-support-aws-secret-manager-plus-native branch 2 times, most recently from 525f7d8 to 9420598 Compare January 29, 2025 14:23
@JiriOndrusek JiriOndrusek marked this pull request as ready for review January 29, 2025 14:23
@JiriOndrusek JiriOndrusek force-pushed the full-support-aws-secret-manager-plus-native branch from 9420598 to 0f43f72 Compare January 30, 2025 07:07
@jamesnetherton
Copy link
Contributor

Tests failed:

java.lang.IllegalArgumentException: Error configuring property: camel.component.aws-cw.secret-key because cannot find component with name aws-cw. Make sure you have the component on the classpath

@JiriOndrusek
Copy link
Contributor Author

Tests failed:

java.lang.IllegalArgumentException: Error configuring property: camel.component.aws-cw.secret-key because cannot find component with name aws-cw. Make sure you have the component on the classpath

I'll check that

@JiriOndrusek
Copy link
Contributor Author

That is my fault, I changed something in aws-test-support, let me fix it

@JiriOndrusek JiriOndrusek force-pushed the full-support-aws-secret-manager-plus-native branch from 0f43f72 to 410fb3b Compare January 30, 2025 13:42
@JiriOndrusek
Copy link
Contributor Author

I missed some hardcoded aws2-*. It is fixed now.

@JiriOndrusek JiriOndrusek force-pushed the full-support-aws-secret-manager-plus-native branch from 410fb3b to 24e8142 Compare January 30, 2025 14:01
Copy link
Contributor

@aldettinger aldettinger left a comment

Choose a reason for hiding this comment

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

Few nitpicks, looks good beyound.

Maybe there is need for more coverage like auto reload in other prs.

@JiriOndrusek JiriOndrusek force-pushed the full-support-aws-secret-manager-plus-native branch from 24e8142 to ccccbeb Compare January 31, 2025 10:47
@JiriOndrusek
Copy link
Contributor Author

JiriOndrusek commented Jan 31, 2025

Maybe there is need for more coverage like auto reload in other prs.

Do you mean a use case with context reload? it is covered by different test class, which already exists (see https://github.com/apache/camel-quarkus/blob/main/integration-tests-jvm/aws-secrets-manager/src/test/java/org/apache/camel/quarkus/component/aws/secrets/manager/it/CamelContextRefreshOnSecretRefreshTest.java)

@JiriOndrusek
Copy link
Contributor Author

failure in saga example seems to be unrelated

@aldettinger
Copy link
Contributor

Maybe there is need for more coverage like auto reload in other prs.

Do you mean a use case with context reload? it is covered by different test class, which already exists (see https://github.com/apache/camel-quarkus/blob/main/integration-tests-jvm/aws-secrets-manager/src/test/java/org/apache/camel/quarkus/component/aws/secrets/manager/it/CamelContextRefreshOnSecretRefreshTest.java)

Yes, more generally the question is whether all features mentioned in the camel documentation are covered with tests ;)

@JiriOndrusek
Copy link
Contributor Author

Yes, more generally the question is whether all features mentioned in the camel documentation are covered with tests ;)

That is a valid question, I'm currently adding test coverage into azure-key-vault and I noticed feature related to context refresh, which might not be covered fully in aws. I'm switching to draft and wI'll revisit this PR again once azure one is done.

@JiriOndrusek JiriOndrusek marked this pull request as draft January 31, 2025 14:05
@aldettinger
Copy link
Contributor

Yes, more generally the question is whether all features mentioned in the camel documentation are covered with tests ;)

That is a valid question, I'm currently adding test coverage into azure-key-vault and I noticed feature related to context refresh, which might not be covered fully in aws. I'm switching to draft and wI'll revisit this PR again once azure one is done.

@JiriOndrusek This great pr already add a lot of value. Follow ups could be other prs. WDYT ?

@JiriOndrusek JiriOndrusek marked this pull request as ready for review February 3, 2025 07:08
@JiriOndrusek
Copy link
Contributor Author

Yes, more generally the question is whether all features mentioned in the camel documentation are covered with tests ;)

That is a valid question, I'm currently adding test coverage into azure-key-vault and I noticed feature related to context refresh, which might not be covered fully in aws. I'm switching to draft and wI'll revisit this PR again once azure one is done.

@JiriOndrusek This great pr already add a lot of value. Follow ups could be other prs. WDYT ?

That's right. Let's merge this one and if anything is missing (which I'm not sure at the moment, as I discovered that the feature I thought about is covered), a new PR can be added.

@jamesnetherton jamesnetherton merged commit 14ffedb into apache:main Feb 3, 2025
23 of 24 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
Development

Successfully merging this pull request may close these issues.

Aws-secrets-manager: minor improves to test coverage
4 participants