[GitHub] [cloudstack-cloudmonkey] borisstoyanov commented on issue #94: add human readable output

borisstoyanov commented on issue #94: URL: https://github.com/apache/cloudstack-cloudmonkey/issues/94#issuecomment-1423735115 @Pearl1594 are you still looking to work on this issue? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to G

[GitHub] [cloudstack-cloudmonkey] borisstoyanov commented on issue #117: filter is ignored on e.g. deploy virtual machine

borisstoyanov commented on issue #117: URL: https://github.com/apache/cloudstack-cloudmonkey/issues/117#issuecomment-1423726653 @DaanHoogland I'm working on the milestone for 6.3.0 and I'm wondering should we add this improvement. Do you have any idea how much effort it is going to take, a

[GitHub] [cloudstack-cloudmonkey] borisstoyanov commented on pull request #52: Add new filter based on jmespath for 6.0 version

borisstoyanov commented on PR #52: URL: https://github.com/apache/cloudstack-cloudmonkey/pull/52#issuecomment-1423721674 @snifbr could you please resolve the conflicts -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

[GitHub] [cloudstack-cloudmonkey] borisstoyanov commented on pull request #84: Follow standard project layout

borisstoyanov commented on PR #84: URL: https://github.com/apache/cloudstack-cloudmonkey/pull/84#issuecomment-1422622686 @davidjumani could you please address the conflicts -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

[GitHub] [cloudstack-cloudmonkey] borisstoyanov closed issue #98: Auto-complete not working for 'id' param in update storagecapabilities

borisstoyanov closed issue #98: Auto-complete not working for 'id' param in update storagecapabilities URL: https://github.com/apache/cloudstack-cloudmonkey/issues/98 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the UR

[GitHub] [cloudstack-cloudmonkey] borisstoyanov merged pull request #111: Support for auto-completion of storage pool related APIs

borisstoyanov merged PR #111: URL: https://github.com/apache/cloudstack-cloudmonkey/pull/111 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubsc

[GitHub] [cloudstack-cloudmonkey] borisstoyanov commented on pull request #112: Enable passing of profile information via commandline

borisstoyanov commented on PR #112: URL: https://github.com/apache/cloudstack-cloudmonkey/pull/112#issuecomment-1422612881 Hi @Pearl1594 I've tried using the parameters but could not, could you please tell me what I'm doing wrong? ``` bstoyanov@MacBookProlocal cloudstack-cloudmon

[GitHub] [cloudstack-kubernetes-provider] DaanHoogland closed pull request #38: deployment.yaml: add tolerations

DaanHoogland closed pull request #38: deployment.yaml: add tolerations URL: https://github.com/apache/cloudstack-kubernetes-provider/pull/38 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specif

Re: [DISCUSS] CloudStack Website build and modernisation

All, The ASF infra has advised recently that they're deprecating and removing Roller support, our project blog is based on Roller. Given this hasn't received any objections on this thread, I've spent some time in the last two months exploring options that solve most of our website and blog req

Re: [DISCUSSION] Management of the database's "VIEW"s

I like your ideas as well @Rohit Yadav and @Wei ZHOU , but that is a step further than what Daniel is proposing and his idea is a good step forward. As for the schema-create-views.sql, that would be possible and maybe even neater to split in a schema-drop-views.sql to be run before upgrades and t

Re: [DISCUSSION] Management of the database's "VIEW"s

I totally agree with Rohit. Anyway, it is a very nice idea. It will be very helpful when we make SQL changes on VIEWs on both a fork and main branch. Can we have all views in a separated file, for example schema-create-views.sql, and run the SQL as the last step when all other SQL changes are don