nebula-orchestrator / nebula-python-sdk Goto Github PK

Expected/Wanted Behavior

The PyPI description should match the GitHub readme.

Actual Behavior

The PyPI description field is empty.

There should be a full CI\CD (TravisCI based most likely) that autopushes the SDK to the PyPi whenever an update is made to the Repo.

While currently possible to have Port configured in the "host" param like "nebula.host.com:8888" it deserves it's own "port" param when you create the connection to a nebula server.

Dependabot couldn't authenticate with https://pypi.python.org/simple/.

You can provide authentication details in your Dependabot dashboard by clicking into the account menu (in the top right) and selecting 'Config variables'.

View the update logs.

Expected/Wanted Behavior

All prereqs at requirements.txt needs to up to date

Actual Behavior

Some packages are outdated

Expected/Wanted Behavior

Similar to what's been done in https://github.com/naorlivne/parse_it Travis CI should be configured that whenever the version of the sdk is changed to do the following:

1. create a new tag of the matching version
2. create a new release of the matching version (should also create the tag)
   3, create a new branch of the matching version
3. use naorlivne/github-changelog-generator-dockerized docker container to auto create a changelog and push it to the repo

Actual Behavior

There are no release notes\changelog & all version branches & tags are manually created.

Expected/Wanted Behavior

https://codecov.io/ should be added to know what the code coverage is as well as a badge of it

Actual Behavior

there is no code coverage tool

Noticed I forget that endpoint in the SDK

Expected/Wanted Behaviour

The version of the SDK should be auto set to match the branches (and ignore the master branch as it's not the one that should be deployed from to PyPi but rather only valid numbered version branches).

the $TRAVIS_BRANCH envvar will likely be part of the solution but as this should be a change in the codebase itself (rather then just assigning the variable value a more complex solution the just os.getenv(TRAVIS_BRANCH) will be needed.

Possible solutions (need to read more about them):

• https://pypi.org/project/bump2version/
• https://pypi.org/project/changes/
• https://pypi.org/project/zest.releaser/

Actual Behaviour

Version is manually set before deployments.

Currently the requirements.txt is a mess, each repo should only include the requirements it actaully needs to function and not have grabage that was either once needed but not anymore or needed by another repo in the Nebula project but not this repo.

Expected/Wanted Behaviour

With Python 2.x nearing it's EOL Nebula should migrate to Python 3.x (with the current minor version target being the latest released version)

Actual Behaviour

Nebula is is currently Python 2.7.x based