-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Deprecate Joyent API #54211
Comments
We've (https://mnx.io) been handling Joyent EOL refugees, and run the same Triton stack. I'd like consideration for a cloud provider rename, or maybe a better solution would be to rename this API to |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
Thank you for updating this issue. It is no longer marked as stale. |
The deprecation cycle is described in the documentation: https://docs.saltstack.com/en/latest/topics/development/deprecations.html "A deprecation warning should be in place for at least two major releases before the deprecated code and its accompanying deprecation warning are removed. More time should be given for more complex changes." Core team will review and update the issue. |
@Akm0d do you have an opinion on how to handle this deprecation? |
We'll put it off for now until more is done for openstack/joyent/trident in idem-cloud |
Description of Issue
Joyent is EOL as of November 9, 2019. It's API in salt needs to be deprecated in the current release and removed from the next release
The text was updated successfully, but these errors were encountered: