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

Adding an extension to archive workflows in S3 bucket #252

Merged
merged 1 commit into from
Oct 5, 2024

Conversation

junaidHussain-clari
Copy link
Contributor

@junaidHussain-clari junaidHussain-clari commented Sep 3, 2024

Pull Request type

  • Bugfix
  • Feature
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • WHOSUSING.md
  • Other (please describe):

NOTE: Please remember to run ./gradlew spotlessApply to fix any format violations.

Changes in this PR
In this PR, we've added a new option to start saving workflows to S3. To use this feature, set the workflowArchivalType property to S3. You can also set a time-to-live (TTL) for how long workflows should be kept before archiving. Additionally, there's a new property called workflowArchiveUnsuccessfulOnly that allows you to archive only the workflows that failed.

Describe the new behavior from this PR, and why it's needed
This PR lets you save workflows to S3. To do this, set the workflowArchivalType property and provide the bucket name and region also if needed. You can also choose to only archive failed workflows to save on storage costs by setting the workflowArchiveUnsuccessfulOnly property. Path on S3 bucket will be workflow_name/workflow_id.

Alternatives considered

Describe alternative implementation you have considered

@v1r3n v1r3n merged commit 3b6a9c0 into conductor-oss:main Oct 5, 2024
2 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.

2 participants