[PAX-11407] [merge after 8/25] removing client_secret_env_key from manifest #83
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.
Summary
Jira ticket: https://jira.tinyspeck.com/browse/PAX-11407
client_secret_env_key
became redundant and the internal 3p auth users are supposed to be using a new subcommandadd-secret
instead of the .env variableclient_secret_env_key
from the SDK objectadd-secret
subcommand is available to the end user.How to test:
client_secret_env_key
field becomes optional in the PRimport_map.json
fileclient_secret_env_key
fieldclient_secret
andclient_secret_env_key
field should be empty in theproviders
table in dbimport.map file example:
Manifest.ts file in app file example:
Requirements (place an
x
in each[ ]
)