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

Deprecate Joyent API #54211

Closed
Akm0d opened this issue Aug 14, 2019 · 7 comments
Closed

Deprecate Joyent API #54211

Akm0d opened this issue Aug 14, 2019 · 7 comments
Assignees
Labels
Deprecation severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around won't-fix legitimate issue, but won't fix
Milestone

Comments

@Akm0d
Copy link
Contributor

Akm0d commented Aug 14, 2019

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

@Akm0d Akm0d added P4 Priority 4 ZRELEASED - Neon retired label v2019.2.1 unsupported version develop Pointing to develop branch; needs rebase labels Aug 14, 2019
@Akm0d Akm0d added this to the Approved milestone Aug 14, 2019
@Akm0d Akm0d self-assigned this Aug 14, 2019
@nwilkens
Copy link

nwilkens commented Oct 21, 2019

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 Triton.

@Akm0d Akm0d removed the develop Pointing to develop branch; needs rebase label Dec 13, 2019
@stale
Copy link

stale bot commented Jan 12, 2020

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.

@stale stale bot added the stale label Jan 12, 2020
@sagetherage
Copy link
Contributor

@Ch3LL

@stale
Copy link

stale bot commented Jan 15, 2020

Thank you for updating this issue. It is no longer marked as stale.

@stale stale bot removed the stale label Jan 15, 2020
@sagetherage
Copy link
Contributor

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.

@sagetherage sagetherage added severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around P2 Priority 2 ZRelease-Sodium retired label Confirmed Salt engineer has confirmed bug/feature - often including a MCVE and removed v2019.2.1 unsupported version ZRELEASED - Neon retired label P4 Priority 4 labels Jan 15, 2020
@sagetherage sagetherage removed Confirmed Salt engineer has confirmed bug/feature - often including a MCVE ZRelease-Sodium retired label labels May 22, 2020
@sagetherage sagetherage reopened this May 22, 2020
@sagetherage sagetherage added the Magnesium Mg release after Na prior to Al label May 22, 2020
@sagetherage sagetherage removed the P2 Priority 2 label Jun 3, 2020
@sagetherage sagetherage modified the milestones: Approved, Magnesium Jul 29, 2020
@sagetherage
Copy link
Contributor

@Akm0d do you have an opinion on how to handle this deprecation?

@Akm0d Akm0d closed this as completed Aug 17, 2020
@Akm0d
Copy link
Contributor Author

Akm0d commented Aug 17, 2020

We'll put it off for now until more is done for openstack/joyent/trident in idem-cloud

@sagetherage sagetherage added won't-fix legitimate issue, but won't fix and removed Magnesium Mg release after Na prior to Al labels Aug 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Deprecation severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around won't-fix legitimate issue, but won't fix
Projects
None yet
Development

No branches or pull requests

4 participants