Feature: Add connection libraries to the superset instance
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- devops, infrastructure
Research direction
No files, tests, or entry points are identified in the issue. Start by reviewing the Superset image and CRD design to compare common connectors with user-specified Python packages; done means an agreed implementation scope, security model, and versioning behavior.
Written by the indexing model from the issue text.
Description
Current Situation
if a user want's to have e.g. mssql as a database connector present in a superset instance, he'd need to either
- Build a custom image using
pip install pymssql - kubectl exec -- pip install pymssql
- Overrite startup commands to execute pip install pymssql
a list of possible connector options can be found here
Proposal
As a platform provider we should enable a user to be flexible and on the other hand ensure that our images are as lean and secure as possible.
Option 1
Include common connectors in our image.
Upside
- User has maintained and out of the box images that "just work" for their purposes
- Stackable has full control over versioning and can ensure and guarantee that specific scenarios will work
- Low hanging fruit ( up to decision on what include, that might be bigger than it seems )
Downside
- We'd need to be responsible for upcoming bugs, CVE's as well as maintaining library versions.
- Larger images and delivery of not needed software
Option 2
Allow users to specify python packages to install in crds
Upside
- Users can specify the libraries they want to be installed
- Lean and secure base images
- No maintenance on Stackable end needed
- Mechanism might be reusable for Airflow
Downside
- Open up the installation to malicious software
- Needs to be an Override as we can't take guarantee of user defined packages
- Larger development efforts expected
- Dominant language
- Rust
- Stars
- 35
- Forks
- 4
- Avg merge
- 12h 20m
- Merged PRs (30d)
- 10
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stackabletech/superset-operator
-
customer-request
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
OPA roles are only resolved at login, so role changes and offboarding don't reach live sessions Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
stackabletech/superset-operator#667 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
stackabletech/superset-operator#661 · 4 comments ·
-
type/feature-new
Difficulty 5/5 Over a week Newbie friendliness 25/100
stackabletech/superset-operator#618 · 1 comment ·
All issues in stackabletech/superset-operator
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
TheLarkInn/aipm#2413 ·
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
alexgorbatchev/simple-ptt#15 ·
-
tooling
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
todo:ticket
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
taikoxyz/taiko-mono#22168 · 1 comment ·