-
Notifications
You must be signed in to change notification settings - Fork 79
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
Make sure to display old deprecated instance sizes #939
Conversation
Hey @loosla, thanks for helping me out by approving the actions and merging main. Could you check out the failing pipeline? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @lauhon,
Thanks for the PR. I've made some suggestions inline.
Admittedly, I am a bit reluctant about this one. We are intentionally discouraging new usage of these plans as they will go away at some point in the future. Though marking them as deprecated and adding a bit of a disclaimer should be a good compromise.
example: apps-s-1vcpu-0.5gb | ||
example: apps-s-1vcpu-0.5gb | ||
|
||
old_instance_size_slug: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
specification/resources/apps/models/app_component_instance_base.yml
Outdated
Show resolved
Hide resolved
Co-authored-by: Andrew Starr-Bochicchio <[email protected]>
Thanks a lot @andrewsomething! I applied your suggestions :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 LGTM, thanks for applying the changes!
Hi,
I'm not entirely sure if this is valid. But I noticed that the old instance slugs still work, but are not part of the schema.
My idea is to display them, but as deprecated. This would be great for the project Im working on, because we still use those old slugs and would benefit from them being present in the API spec.