-
Notifications
You must be signed in to change notification settings - Fork 55
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
Add support for PCF App Autoscaler CLI Plugin #110
Comments
Other forks achieved what @niharbabu99 is requesting https://github.com/EngineerBetter/cf-cli-resource. It would be great if there was a distribution with some of the most used plugins. |
This has been requested before (#67) but, unfortunately, I can't legally package the Pivotal App Autoscaler CLI Plugin in the And of course the EULA is filled with lots of restrictions:
Given the restrictions with the VMware EULA, the only way I think I can legally add this functionality is to work in a "bring your own cf cli plugin" framework where your pipeline could supply the plugin to the Open to ideas on this one... |
I think "bring your own cf cli plugin" is great idea and it helps many users who uses this resource. If it can be achieved, it would be very great. |
I'll explore implementing something like this with the Pivotal App Autoscaler CLI Plugin as a reference use-case. I will need help testing this as I do not have a PCF environment to test against. Is this something you can help me test when the time is right? |
@patrickcrocker sure I can help with testing when the feature is ready. Please tag me when needed so that I can plan and take some time to validate it. |
Having the auto scaler plugin and its commands added to cf-cli resource will be helpful to create autoscale rules for PCF apps.
Currently, we are adding autoscale rules for our micro-services that are deployed in PCF using the auto-scale feature described here.
Currently, we are using tasks to accomplish this by having a plugin installed in our image. If it can be integrated with cf-cli resource it would be easy to use.
The text was updated successfully, but these errors were encountered: