Skip to content

CAMEL-19615: fix chmodDirectory option to not try to change the directory permission for existing directory#10726

Closed
michael-salzburg wants to merge 509 commits intoapache:mainfrom
michael-salzburg:chmoddir-error
Closed

CAMEL-19615: fix chmodDirectory option to not try to change the directory permission for existing directory#10726
michael-salzburg wants to merge 509 commits intoapache:mainfrom
michael-salzburg:chmoddir-error

Conversation

@michael-salzburg
Copy link
Contributor

Description

The current chmodDirectory option implementation try to change each directory part and fails if it cannot change the permission. The expected behavior is that only for new directory parts the permission is changed/set.

Target

  • I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

  • If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

  • I checked that each commit in the pull request has a meaningful subject line and body.
  • I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

Croway and others added 30 commits March 16, 2023 17:27
Signed-off-by: Andrea Cosentino <ancosen@gmail.com>
…es consumer (#9589) (#9596)

- Issues returned are already ordered descendant - do not revert the order of issues a 2nd time
- Make sure to exit polling loop early when no further issues are returned (total # of issues returned is lower than query page size)
- Avoid duplicates in returned issue list
- Adjust query page size according to given max results limitation
- Fix ordering of mocked issue return values in unit tests (mocks should return issues in descendant order)
- Add more unit tests on new issues consumer (testing filter offset, pagination, duplicates)
* CAMEL-19155 Re-throw exceptions in `ServiceBusConsumer`

If an exception occurred during Exchange processing, the exception must
be rethrown in the message receive and error handlers to trigger the
`ServiceBusReceiverAsyncClient` to abandon the message so that the
message is requeued.

* Revert "CAMEL-19155 Re-throw exceptions in `ServiceBusConsumer`"

This reverts commit a2efbed.

* CAMEL-19155 - Explicitly complete/abandon Azure Service Bus messages

Taking control of message complete/abandon when auto-complete is
enabled, since allowing the Service Bus client to do this automatically
causes messages to be completed even if the Exchange failed because
errors do not propagate back to the reactive message Publisher.

* CAMEL-19155 - Add explanatory comment

* CAMEL-19155 - Correct explanatory comment

---------

Co-authored-by: Dylan Piergies <Dylan.Piergies@tesco.com>
…AMEL-18636 additional auth options (#9567)

* CAMEL-19152 - Add file client header and flush option

* CAMEL-18636: Allow string based auth + additional auth methods

* CAMEL-18636: Add security label to config parameters

* CAMEL-18636: Fixed setting SAS credentials from registry

* camel-jbang - Fix NPE

* CAMEL-19152 - Add file client header and flush option

* CAMEL-18636: rebase - removed validate method from component

* CAMEL-18636: Add security label to config parameters

* CAMEL-18636: Fixed setting SAS credentials from registry

---------

Co-authored-by: Andreas Klug (BD/XDE1) <KGA8FE@fe-c-014an.fritz.box>
Co-authored-by: Claus Ibsen <claus.ibsen@gmail.com>
…wn cache manager, which prevents from the component to be restarted again.
…nt filters are evaluated in order of their priority property, and updated tests. (#9638)
davsclaus and others added 16 commits June 20, 2023 12:03
…ed events to avoid showing sensitive data such as passwords from URIs
Signed-off-by: Andrea Cosentino <ancosen@gmail.com>
When an authentication error is thrown by Kafka, this could cause an endless loop in the client. Potentially affecting the Kafka broker due to an excessive connection retries in a short period.

This prevents authentication related errors to cause this.
Refactored code in SftpOperations.java to ensure chmod is only called after successful directory creation to prevent potential failures.
@michael-salzburg
Copy link
Contributor Author

typo on pull request. will create a new one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.