-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Support subresources, e.g. scale, deploymentrollback, etc #417
Comments
Has there been any updates on that topic? |
This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions! |
Any update ? |
@XciD : Unfortunately I haven't been able to find time to fix this. Could you please create a PR to support these if you have bandwidth? |
This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions! |
Found this by noticing that the |
@jglick : Thanks for pointing this out. I also think we should use designated api. So for starting what resources shall we consider adding support in model/DSL? I have these in mind:
|
+ Changed extensions/Scale to autoscaling/Scale + Added tests
+ Changed extensions/Scale to autoscaling/Scale + Added tests
+ Changed extensions/Scale to autoscaling/Scale + Added tests
+ Changed extensions/Scale to autoscaling/Scale + Added tests
Certain operations are applicable via subresources rather than updating the resource. We need a general way to support this as it's important for authorization policies that allow updating via subresources but not the resource itself.
The text was updated successfully, but these errors were encountered: