chore: deprecate no longer supported projectId and environment config settings #240
Conversation
This file contains 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
thomasheartman
approved these changes
Sep 17, 2024
daveleek
deleted the
chore/deprecate-projectid-and-environment-config-settings
branch
|
What documentation explains how to switch off of using Environment? I see no documentation of scope at |
|
@rcollette This is briefly mentioned in the deprecation notice, but environment and project scope in Unleash is controlled with your api token. The docs for that are at https://docs.getunleash.io/reference/api-tokens-and-client-keys. Does that answer your question? |
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.
Deprecates ProjectId and Environment properties of UnleashSettings with an upcoming removal notice and gentle push towards API token scopes.