Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: add a warning when using the newer service environments #809

Closed
threepointone opened this issue Apr 15, 2022 · 4 comments · Fixed by #813 or #780
Closed

fix: add a warning when using the newer service environments #809

threepointone opened this issue Apr 15, 2022 · 4 comments · Fixed by #813 or #780
Assignees

Comments

@threepointone
Copy link
Contributor

Service environments aren't ready for widespread usage, and the behaviour is guaranteed to change. So we should have a warning if anyone tries to use it.

@threepointone threepointone added this to the 2.0 milestone Apr 15, 2022
@JacobMGEvans JacobMGEvans self-assigned this Apr 15, 2022
@JacobMGEvans
Copy link
Contributor

I can add messaging Monday.

@threepointone
Copy link
Contributor Author

I'll do this one myself, I want to land it soon and do a release this weekend.

threepointone added a commit that referenced this issue Apr 16, 2022
Service environments are not ready for widespread usage, and their behaviour is going to change. This adds a warning if anyone uses them.

Closes #809
threepointone added a commit that referenced this issue Apr 16, 2022
Service environments are not ready for widespread usage, and their behaviour is going to change. This adds a warning if anyone uses them.

Closes #809
threepointone added a commit that referenced this issue Apr 16, 2022
Service environments are not ready for widespread usage, and their behaviour is going to change. This adds a warning if anyone uses them.

Closes #809
JacobMGEvans pushed a commit that referenced this issue Apr 16, 2022
Service environments are not ready for widespread usage, and their behaviour is going to change. This adds a warning if anyone uses them.

Closes #809
@eugene1g
Copy link

Just saw the new message come up in our stack. Do you have any guesses on when Services might become stable or go GA? Even if as broad as "next quarter / next year".

@threepointone
Copy link
Contributor Author

Probably next quarter, but I can't guarantee tbh, it's a cross functional effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
3 participants