feat(lambda-tiler)!: allow API keys to be disabled BM-1281 #3441
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ccbblin
reviewed
May 8, 2025
blacha
changed the title
tawera-manaena
approved these changes
May 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
We have seen a increase of consumer api keys using scripted methods to pull large amounts of data from basemaps.linz.govt.nz these users should be using bulk data access methods like linz/imagery or limz/elevation, as the keys are only consumer we have no easy way of contacting them.
Our only option is to disable their keys and hope that they reach out.
Modifications
Add a environment variable to allow us to block API keys
Verification
unit tests and further tests in nonprod.