Skip to content

[sc-330106] set keys as password + add presets - #12

Open
yannickbetou-dku wants to merge 4 commits into
release/1.4.0from
chore/dss14-sc-330106-chore-migrate-string-sensitive-param-to
Open

[sc-330106] set keys as password + add presets#12
yannickbetou-dku wants to merge 4 commits into
release/1.4.0from
chore/dss14-sc-330106-chore-migrate-string-sensitive-param-to

Conversation

@yannickbetou-dku

Copy link
Copy Markdown
Contributor

No description provided.

@alexandremgo

Copy link
Copy Markdown

Comment thread python-lib/dataframe_forward_geocoding.py
Comment thread python-lib/dataframe_reverse_geocoding.py
Comment thread parameter-sets/google_geocoder_auth/parameter-set.json
@alexandremgo
alexandremgo force-pushed the chore/dss14-sc-330106-chore-migrate-string-sensitive-param-to branch from 10a60ad to 83e5458 Compare August 4, 2026 14:52
@alexandremgo
alexandremgo changed the base branch from master to release/1.4.0 August 4, 2026 14:53
@alexandremgo

Copy link
Copy Markdown

Review, with Google Geocoding API & OpenCage

On a DSS instance without the changes, plain password:

Reverse with Google:
Screenshot 2026-08-05 at 16 28 30

Forward with OpenCage:
Screenshot 2026-08-05 at 16 28 43

AFTER the changes: using password type param, keeping the previous existing values

Reverse with Google:
Screenshot 2026-08-05 at 16 33 38

Forward with OpenCage:
Screenshot 2026-08-05 at 16 33 50

Plugin presets

Plugin presets can be created:

For Google:
Screenshot 2026-08-05 at 16 41 32

For OpenCage (and similar Geocoding API with only an API key):

Screenshot 2026-08-05 at 16 42 16

Then those plugin presets can be use in each recipe.

Reverse with Google:
Screenshot 2026-08-05 at 16 42 44

Forward with OpenCage:
Screenshot 2026-08-05 at 16 43 16

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