This repository has been archived by the owner on Jul 14, 2021. It is now read-only.
Use stronger language when warning about native API. #317
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
We don't have a clear upgrade path on the server side for folks using the preview versions of the new policyfile APIs; it's likely that some data, such as policyfile lock documents, will be missing fields that we expect to be required in the final version of the API. Therefore it's unlikely that we'll provide an upgrade mechanism for these documents, and instead will probably just delete them if a user has any data created with a preview version of the API. This warning makes that risk clear for anyone trying the feature.
|
|
|
Thanks for this. 🎸 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
We don't have a clear upgrade path on the server side for folks using
the preview versions of the new policyfile APIs; it's likely that some
data, such as policyfile lock documents, will be missing fields that we
expect to be required in the final version of the API. Therefore it's
unlikely that we'll provide an upgrade mechanism for these documents,
and instead will probably just delete them if a user has any data
created with a preview version of the API. This warning makes that risk
clear for anyone trying the feature.
@sdelano @chef/client-engineers