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

Move Arangodb to new provider structure #46124

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Prab-27
Copy link
Contributor

@Prab-27 Prab-27 commented Jan 27, 2025

Related: #46045


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

@potiuk potiuk force-pushed the move-arangodb-to-new-provider-strcucture branch from f78dd50 to baf13ab Compare January 27, 2025 19:02
@potiuk
Copy link
Member

potiuk commented Jan 27, 2025

Rebased it after fixing the http provider issue

@potiuk potiuk force-pushed the move-arangodb-to-new-provider-strcucture branch from baf13ab to 6115777 Compare January 30, 2025 08:39
@potiuk
Copy link
Member

potiuk commented Jan 30, 2025

One link to moved example needs to be fixed @Prab-27

@potiuk
Copy link
Member

potiuk commented Jan 30, 2025

And conflicts to resolve now :(

@Prab-27
Copy link
Contributor Author

Prab-27 commented Jan 30, 2025

And conflicts to resolve now :(

Sorry, I used GitHub workflow to resolve the conflict. I should have manually done a rebase
Should I revert this changes ?

``python-arango`` ``>=7.3.2``
================== ==================

The changelog for the provider package can be found in the
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@potiuk
Copy link
Member

potiuk commented Jan 30, 2025

No - you neeed to localy rebase and resolve conflicts (and run pre-coomit etc.).. But might be easier to do it again

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.

3 participants