+1 on what Pearl said.
ACS's adoption is increasing extremely fast, I've never heard of any potential
or current operators having any issues with the versioning number (I definitely
didn't when operating ACS from 4.1 up to 4.15).
-Original Message-
From: Pearl d'Silva
Sent: 10 Dec
Pearl1594 closed pull request #151: VM details not getting updated
URL: https://github.com/apache/cloudstack-terraform-provider/pull/151
--
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 c
CodeBleu opened a new pull request, #150:
URL: https://github.com/apache/cloudstack-terraform-provider/pull/150
Provide more info about using the `details` parameter
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
CodeBleu commented on issue #58:
URL:
https://github.com/apache/cloudstack-terraform-provider/issues/58#issuecomment-2532523259
Wondering if this is also related -
https://github.com/apache/cloudstack-terraform-provider/issues/149
--
This is an automated message from the Apache Git Servi
CodeBleu commented on issue #58:
URL:
https://github.com/apache/cloudstack-terraform-provider/issues/58#issuecomment-2531808482
@vishesh92
I'm still having this issue -
https://github.com/apache/cloudstack-terraform-provider/issues/148
--
This is an automated message from the Apache
Hello Daan, all
We have already brought this discussion back and forth between different
media (ML->Github Discussions->ML) and from the feedback we got from the
community, I believe that the discussion should stay on the ML, where
the final vote will be held ("If it didn't happen on the maili
Hi,
I wouldn't say that our current release naming strategy in anyway gives the
wider community and consumers the idea that this project is dead or stagnating.
There has been an increase in adoption, that said, I do not oppose renaming the
upcoming release to CloudStack 5 or anything else for t
