kiranchavala commented on issue #29:
URL:
https://github.com/apache/cloudstack-terraform-provider/issues/29#issuecomment-1978067391
@synergiator are you still facing the issue, can i go ahead and close the
issue if its resolved
--
This is an automated message from the Apache Git
kiranchavala closed issue #47: cannot unmarshal object into Go struct field
RegisterTemplateResponse.template of type string
URL: https://github.com/apache/cloudstack-terraform-provider/issues/47
--
This is an automated message from the Apache Git Service.
To respond to the message, please
kiranchavala commented on issue #47:
URL:
https://github.com/apache/cloudstack-terraform-provider/issues/47#issuecomment-1978057738
Thanks @ccycv Closing the issue as its resolved
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
Thanks for stepping up and sharing your plan.
Regards.
From: Suresh Kumar Anaparti
Sent: Monday, March 4, 2024 5:36:55 PM
To: us...@cloudstack.apache.org
Cc: dev@cloudstack.apache.org
Subject: Re: [PROPOSE] RM for Cloudstack Terraform Provider
+1, on the
+1, on the timelines.
Nice to see terraform provider release after a long time, thanks for
volunteering Kiran!
Regards,
Suresh
On Mon, Mar 4, 2024 at 5:30 PM Kiran Chavala
wrote:
> Hi All,
>
> Greetings
>
> I'd like to propose and put myself forward as the release manager for
> v0.5.0 release
btzq commented on issue #75:
URL:
https://github.com/apache/cloudstack-terraform-provider/issues/75#issuecomment-1976429789
GOOD! Someone raised this as a feature request!
Right now in our environment, we provision the infra with terraform, and
deploy our apps with ansible.
Hi All,
Greetings
I'd like to propose and put myself forward as the release manager for v0.5.0
release of
cloudstack-terraform-provider(https://github.com/apache/cloudstack-terraform-provider)
if no objections are there.
Since the last release of the cloudstack-terraform-provider (v0.4.0)
fabiomatavelli commented on code in PR #64:
URL:
https://github.com/apache/cloudstack-terraform-provider/pull/64#discussion_r1510994351
##
.github/workflows/testacc.yml:
##
@@ -0,0 +1,79 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor
sbrueseke commented on PR #78:
URL: https://github.com/apache/cloudstack-go/pull/78#issuecomment-1976323997
@weizhouapache @rohityadavcloud can you please review this PR?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
weizhouapache commented on PR #77:
URL: https://github.com/apache/cloudstack-go/pull/77#issuecomment-1976309995
> Another alternative approach I can think of is generating multiple modules
as per the ACS version. Every release of cloudstack-go will have multiple
modules for different
vishesh92 commented on PR #77:
URL: https://github.com/apache/cloudstack-go/pull/77#issuecomment-1976261911
If someone upgrades their cloudstack-go SDK and builds their project, the
build will fail only if some method which is now changed is being used. Any
good IDE should be able to list
vishesh92 commented on code in PR #64:
URL:
https://github.com/apache/cloudstack-terraform-provider/pull/64#discussion_r1510811590
##
.github/workflows/testacc.yml:
##
@@ -0,0 +1,79 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license
Hi Ivet,
I would love to do a talk at this event. This time a technical one instead of a
user story if this makes sense.
Regards,
Swen
-Ursprüngliche Nachricht-
Von: Ivet Petrova
Gesendet: Mittwoch, 28. Februar 2024 16:29
An: dev ; us...@cloudstack.apache.org
Cc: Apache CloudStack
13 matches
Mail list logo