-
Notifications
You must be signed in to change notification settings - Fork 2
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
[Merged by Bors] - fixup ability to detect MAP BOX API key and add it to the environment… #178
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Rob, thanks for your PR. Unless I'm missing something, this can be reduced to a single call like this:
cb.add_env_var_from_secret("MAPBOX_API_KEY", &value, "connections.mapBoxApiKey");
similar to the way it's done in lines 401 and 402.
I think @razvan's suggestion is the way to go. Here are also some points that might interest you describing why the current approach of the PR is not optimal. Hope they are helpful :)
|
@sbernauer @razvan - have simplified this to use optional crd property for mapbox api key. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
bors merge |
#178) … if present. ## Description Addition of ability to add the lookup for the MAP_BOX_API key that Superset can use to obtain geo information and map backgrounds for lat / long style queries. Co-authored-by: Razvan-Daniel Mihai <[email protected]>
Pull request successfully merged into main. Build succeeded: |
Great, thanks! |
@sbernauer - yes I think that would make sense. |
… if present.
Description
Addition of ability to add the lookup for the MAP_BOX_API key that Superset can use to obtain geo information and map backgrounds for lat / long style queries.
Review Checklist
Once the review is done, comment
bors r+
(orbors merge
) to merge. Further information