Re: [DISCUSS] Define a release schedule for the project
nice to see this discussion being had again and sorry to be late in replying João, I see no replies have come forward yet. Let's add a new https://github.com/apache/cloudstack/discussions/new/choose for this as well. I still feel my proposal is good and should have been applied. but we can gather all kinds of proposals in one place and get to some kind of improvement someday. One point of criticism on your proposal, though not a breaking point, is that it doesn't guarantee backwards compatibility, something we have always maintained so far (through upgrade paths). Not being chained to old to technical debt is good, but it should not leave people behind ;) We do have a hardly ever used procedure to deprecate old plugins for instance. we should think about applying that to API and other namings as well. regards, On Fri, Mar 15, 2024 at 12:10 PM João Jandre Paraquetti wrote: > > Hi all, > > I had posted this message on another thread, but following Rohit's > advice I've decided to create a new one for it. That being said, I have > another proposal for the versioning scheme. Instead of dropping the "X" > on our X.Y.Z.N, we can set a fixed schedule (that can be further > discussed) for the version changes: > > - Every two years, we release a major version (X), which can contain > changes that break backward compatibility, such as (but not limited to): > removing unused/useless APIs, renaming APIs, and changing the default > behavior of features. These changes must be discussed with the devs and > be properly communicated to the community (via API deprecation, for > example) at least one minor version before the major release; > - Every semester, we release a minor version (Y) of the current major > (X) version, these can contain new features/APIs, as long as the > backward compatibility is maintained; also, feature/API deprecation > should happen on these versions; > - Every 2/3 months, we release patch versions (Z), that fix any bugs > that were released with the major and minor versions, these versions > should not contain any new features; > - In extreme cases (such as with security issues) we work on and release > security versions (N); > > The proposed schedule is only a sketch that can be worked on. However I > believe that the project can benefit from: > 1. A fixed release schedule; > 2. A mechanism to introduce disruptive changes, so that the project can > evolve and not be chained to the same features/API/limitation/technical > debts forever. > > Furthermore, having a schedule allows us to have a project roadmap, that > outlines the future deprecations, changes and big features. > > Best Regards, > > João Jandre. > -- Daan
[PR] Bump golang.org/x/net from 0.0.0-20210805182204-aaa1db679c0d to 0.23.0 [cloudstack-terraform-provider]
dependabot[bot] opened a new pull request, #111: URL: https://github.com/apache/cloudstack-terraform-provider/pull/111 Bumps [golang.org/x/net](https://github.com/golang/net) from 0.0.0-20210805182204-aaa1db679c0d to 0.23.0. Commits See full diff in https://github.com/golang/net/commits/v0.23.0";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/cloudstack-terraform-provider/network/alerts). -- 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-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Update docs for 4.18.2.0 [cloudstack-documentation]
JoaoJandre commented on PR #393: URL: https://github.com/apache/cloudstack-documentation/pull/393#issuecomment-2066449225 > Cheers @JoaoJandre I see the tag and docs are live now, the website is updated too. I think only thing remaining is the ML announcement for you to draft/send. @rohityadavcloud Thanks, the announcement is already drafted, only waiting for the reviews: https://lists.apache.org/thread/hz3d737ok1s6ydnky54c4clsjddlkpfg -- 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-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump golang.org/x/net from 0.17.0 to 0.23.0 [cloudstack-go]
dependabot[bot] opened a new pull request, #82: URL: https://github.com/apache/cloudstack-go/pull/82 Bumps [golang.org/x/net](https://github.com/golang/net) from 0.17.0 to 0.23.0. Commits https://github.com/golang/net/commit/c48da131589f122489348be5dfbcb6457640046f";>c48da13 http2: fix TestServerContinuationFlood flakes https://github.com/golang/net/commit/762b58d1cf6e0779780decad89c6c1523386638d";>762b58d http2: fix tipos in comment https://github.com/golang/net/commit/ba872109ef2dc8f1da778651bd1fd3792d0e4587";>ba87210 http2: close connections when receiving too many headers https://github.com/golang/net/commit/ebc8168ac8ac742194df729305175940790c55a2";>ebc8168 all: fix some typos https://github.com/golang/net/commit/3678185f8a652e52864c44049a9ea96b7bcc066a";>3678185 http2: make TestCanonicalHeaderCacheGrowth faster https://github.com/golang/net/commit/448c44f9287b6745f958d74aa2a17ec7761c2f13";>448c44f http2: remove clientTester https://github.com/golang/net/commit/c7877ac4213b2f859831366f5a35b353e0dc9f66";>c7877ac http2: convert the remaining clientTester tests to testClientConn https://github.com/golang/net/commit/d8870b0bf2f2426fc8d19a9332f652da5c25418f";>d8870b0 http2: use synthetic time in TestIdleConnTimeout https://github.com/golang/net/commit/d73acffdc9493532acb85777105bb4a351eea702";>d73acff http2: only set up deadline when Server.IdleTimeout is positive https://github.com/golang/net/commit/89f602b7bbf237abe0467031a18b42fc742ced08";>89f602b http2: validate client/outgoing trailers Additional commits viewable in https://github.com/golang/net/compare/v0.17.0...v0.23.0";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/cloudstack-go/network/alerts). -- 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-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Add doc for importing and unmanaging volumes [cloudstack-documentation]
andrijapanicsb commented on code in PR #390: URL: https://github.com/apache/cloudstack-documentation/pull/390#discussion_r1572312874 ## source/adminguide/storage.rst: ## @@ -1011,6 +1011,60 @@ Following is the example for checkVolume API usage and the result in the volume }, } + +Importing and Unmanaging Volumes from Storage Pools +~~ + +Since Apache CloudStack 4.19.1.0, importing and unmanaging volumes from primary storage pools are supported. + +.. note:: + Currenty the supported storage types are: NFS, Ceph and Local storage for KVM hypervisor. + +#. Log in to the CloudStack UI as an administrator. + +#. In the left navigation bar, click *Tools > Import DATA Volumes* section. + +#. Select the scope of the storage pool (Zone, Cluster, Host). + +#. Select the zone/pod/cluster/host of the storage pool. + +#. Select the storage pool. + +#. The unmanaged volumes on the storage pool are listed on the left panel. + +#. The managed volumes on the storage pool are listed on the right panel. + +|list-unmanaged-managed-volumes.png| + +To import a volume, + +#. select a unmanaged volume from the left panel, click "Import Volume" icon. + +#. In the Import Volume pop-up, select the Account Type, Domain/Account/Project and a disk offering. + +#. Click OK. + +|import-volume.png| + +.. note:: + The volume to be imported must be placed in the root directory of the storage pool. + The format of the volume should be QCOW2 on NFS/Local storage, and RAW on Ceph storage. + Encrypted volumes cannot be unmanaged or imported. + +.. note:: + By default, the volume is imported for the caller if Domain/Account/Project are not set. By default, the imported volumes use the default disk offering "Default Custom Offering for Volume Import" + (on Shared storages) or "Default Custom Offering for Volume Import - Local" (on Local storages). + +To unmanage volume(s), Review Comment: ```suggestion To unmanage volume(s): ``` -- 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-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Add doc for importing and unmanaging volumes [cloudstack-documentation]
andrijapanicsb commented on code in PR #390: URL: https://github.com/apache/cloudstack-documentation/pull/390#discussion_r1572314144 ## source/adminguide/storage.rst: ## @@ -1011,6 +1011,60 @@ Following is the example for checkVolume API usage and the result in the volume }, } + +Importing and Unmanaging Volumes from Storage Pools +~~ + +Since Apache CloudStack 4.19.1.0, importing and unmanaging volumes from primary storage pools are supported. + +.. note:: + Currenty the supported storage types are: NFS, Ceph and Local storage for KVM hypervisor. + +#. Log in to the CloudStack UI as an administrator. + +#. In the left navigation bar, click *Tools > Import DATA Volumes* section. + +#. Select the scope of the storage pool (Zone, Cluster, Host). + +#. Select the zone/pod/cluster/host of the storage pool. + +#. Select the storage pool. + +#. The unmanaged volumes on the storage pool are listed on the left panel. + +#. The managed volumes on the storage pool are listed on the right panel. + +|list-unmanaged-managed-volumes.png| + +To import a volume, Review Comment: ```suggestion To import a volume: ``` -- 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-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[ANNOUNCEMENT] Apache CloudStack LTS Maintenance Release 4.18.2.0
The Apache CloudStack project is pleased to announce the release of CloudStack 4.18.2.0. The CloudStack 4.18.2.0 release is a maintenance release as part of its 4.18.x LTS branch and contains around 100 fixes and improvements since the CloudStack 4.18.1.0 release. Some of the highlights include: - Enable over-provisioning for SharedMountPoint primary storage - Support for Veeam 11 and 12 - Improvements to Linstore storage plugin integration - Several Hypervisor (VMware, KVM, XenServer) fixes and improvements - Several UI fixes and improvements - Several Network (L2, VXLAN, etc) fixes and improvements - Several System VM (CPVM, SSVM) fixes and improvements CloudStack LTS branches are supported for 18 months and will receive updates for the first 12 months and only security updates in the last 6 months. Apache CloudStack is an integrated Infrastructure-as-a-Service (IaaS) software platform that allows users to build feature-rich public and private cloud environments. CloudStack includes an intuitive user interface and rich API for managing the compute, networking, software, and storage resources. The project became an Apache top-level project in March, 2013. More information about Apache CloudStack can be found at: https://cloudstack.apache.org/ # Documentation What's new in CloudStack 4.18.2.0: https://docs.cloudstack.apache.org/en/4.18.2.0/releasenotes/about.html The 4.18.2.0 release notes include a full list of issues fixed, as well as upgrade instructions from previous versions of Apache CloudStack, and can be found at: https://docs.cloudstack.apache.org/en/4.18.2.0/releasenotes/ The official installation, administration, and API documentation for each of the releases are available on our documentation page: https://docs.cloudstack.apache.org/ # Downloads The official source code for the 4.18.2.0 release can be downloaded from our downloads page: https://cloudstack.apache.org/downloads.html In addition to the official source code release, individual contributors have also made convenience binaries available on the Apache CloudStack download page, and can be found at: https://download.cloudstack.org/el/7/ https://download.cloudstack.org/el/8/ https://download.cloudstack.org/el/9/ https://download.cloudstack.org/ubuntu/dists/ https://www.shapeblue.com/packages/
Re: [PR] Implicit host tags on KVM [cloudstack-documentation]
JoaoJandre commented on PR #392: URL: https://github.com/apache/cloudstack-documentation/pull/392#issuecomment-2066727316 @weizhouapache It would be good to have a note explaining that flexible tags must always be explicit -- 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-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Implicit host tags on KVM [cloudstack-documentation]
weizhouapache commented on code in PR #392: URL: https://github.com/apache/cloudstack-documentation/pull/392#discussion_r1572529561 ## source/adminguide/host_and_storage_tags.rst: ## @@ -23,6 +23,18 @@ Host tags - Host tags are responsible for directing VMs to compatible hosts. They are validated with the host tags informed in the compute offerings or in the system offerings. +There are two types of host tags: + +- (Explicit) host tags: the host tags are managed by CloudStack. Cloud operator can set, update, and delete host tags via CloudStack API or GUI. Review Comment: ```suggestion - (Explicit) host tags: the host tags are managed by CloudStack, including the flexible host tags. Cloud operator can set, update, and delete host tags via CloudStack API or GUI. ``` -- 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-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Implicit host tags on KVM [cloudstack-documentation]
weizhouapache commented on PR #392: URL: https://github.com/apache/cloudstack-documentation/pull/392#issuecomment-2066816129 > @weizhouapache It would be good to have a note explaining that flexible tags must always be explicit added @JoaoJandre -- 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-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Implicit host tags on KVM [cloudstack-documentation]
weizhouapache commented on code in PR #392: URL: https://github.com/apache/cloudstack-documentation/pull/392#discussion_r1572679724 ## source/adminguide/host_and_storage_tags.rst: ## @@ -23,6 +23,18 @@ Host tags - Host tags are responsible for directing VMs to compatible hosts. They are validated with the host tags informed in the compute offerings or in the system offerings. +There are two types of host tags: + +- (Explicit) host tags: the host tags are managed by CloudStack, including the flexible host tags. Cloud operator can set, update, and delete host tags via CloudStack API or GUI. +- Implicit host tags: the host tags are not managed by CloudStack API. Review Comment: ```suggestion - Implicit host tags: the host tags are not managed by CloudStack API. Cloud operator cannot use both implicit host tags and flexible host tags. ``` ## source/adminguide/host_and_storage_tags.rst: ## @@ -23,6 +23,18 @@ Host tags - Host tags are responsible for directing VMs to compatible hosts. They are validated with the host tags informed in the compute offerings or in the system offerings. +There are two types of host tags: + +- (Explicit) host tags: the host tags are managed by CloudStack, including the flexible host tags. Cloud operator can set, update, and delete host tags via CloudStack API or GUI. +- Implicit host tags: the host tags are not managed by CloudStack API. + +.. note:: + Currently the implicit host tags are only configurable on KVM hosts. Review Comment: ```suggestion Cloud operator can easily set the implicit host tags per host based on server configurations, for example hardware devices (GPU type, disk type, network card type, etc). Currently the implicit host tags are only configurable on KVM hosts. ``` -- 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-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Installing v0.5.0 gives error about unexpected hash [cloudstack-terraform-provider]
CodeBleu commented on issue #109: URL: https://github.com/apache/cloudstack-terraform-provider/issues/109#issuecomment-2066988550 @rohityadavcloud I just tried on a fresh install ( docker container of ubuntu 22.04 ) and get the same error This issue should prob be re-opened, correct? ``` root@48ce3dabe201:/# tofu init Initializing the backend... Initializing provider plugins... - Finding cloudstack/cloudstack versions matching "0.5.0"... - Installing cloudstack/cloudstack v0.5.0... ╷ │ Error: Failed to install provider │ │ Error while installing cloudstack/cloudstack v0.5.0: checksum list has unexpected SHA-256 hash │ af68c90c16b98d249ad01b9215e0dbcb66cb9de21cb3f977cc73b78d80a90413 (expected │ 34ace84ac91a9fac1deb1d9ecef12d9478e3b46fd925f6df6811577964cbfcfe) ``` -- 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-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Add doc for importing and unmanaging volumes [cloudstack-documentation]
weizhouapache commented on code in PR #390: URL: https://github.com/apache/cloudstack-documentation/pull/390#discussion_r1572690092 ## source/adminguide/storage.rst: ## @@ -1011,6 +1011,60 @@ Following is the example for checkVolume API usage and the result in the volume }, } + +Importing and Unmanaging Volumes from Storage Pools +~~ + +Since Apache CloudStack 4.19.1.0, importing and unmanaging volumes from primary storage pools are supported. + +.. note:: + Currenty the supported storage types are: NFS, Ceph and Local storage for KVM hypervisor. + +#. Log in to the CloudStack UI as an administrator. + +#. In the left navigation bar, click *Tools > Import DATA Volumes* section. + +#. Select the scope of the storage pool (Zone, Cluster, Host). + +#. Select the zone/pod/cluster/host of the storage pool. + +#. Select the storage pool. + +#. The unmanaged volumes on the storage pool are listed on the left panel. + +#. The managed volumes on the storage pool are listed on the right panel. + +|list-unmanaged-managed-volumes.png| + +To import a volume: + +#. select a unmanaged volume from the left panel, click "Import Volume" icon. + +#. In the Import Volume pop-up, select the Account Type, Domain/Account/Project and a disk offering. + +#. Click OK. + +|import-volume.png| + +.. note:: + The volume to be imported must be placed in the root directory of the storage pool. + The format of the volume should be QCOW2 on NFS/Local storage, and RAW on Ceph storage. + Encrypted volumes cannot be unmanaged or imported. Review Comment: ```suggestion The following volumes cannot be unmanaged or imported: (1) volume is encrypted; (2) volume is locked; (3) volume has a backing file. ``` -- 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-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: Community Over Code North America 2024 - Talk submitting
Hello guys, I discussed with the responsibles and it was decided that the CloudStack talks will not be targeted to an individual track; however, the track "Cloud and runtime" was renamed to "CloudStack, Cloud, and Runtime", due to our expressiveness in it, and we will be co-chairing this track. Thank you to those who submitted talks to the track. Best regards, Daniel Salvador (gutoveronezi) On 12/04/2024 09:36, Gabriel Beims Bräscher wrote: Hi Daniel, Great to hear, I would love to attend this one. And good work at making this happen. Best regards, Gabriel. On Fri, 12 Apr 2024 at 1:01 AM Ivet Petrova wrote: Hey Daniel, Great initiative! Hope more people will submit proposals. I think we posted on socials for the event at some point. Will post today also. Best regards, On 12 Apr 2024, at 3:36, Guto Veronezi wrote: Hello guys, The Community Over Code North America (COCNA) will happen in October 2024 in Denver. The Call For Tracks for this conference occurred between December 2023 and January 2024; however, we (the community) did not engage in the discussion at that time and ended up not having a track for CloudStack in COCNA 2024, like we always had in the past years. Those interested in submitting talks targeted to ACS do so by submitting them to the "Runtime and cloud". However, I am speaking with the responsible for the conference to check if we could put something together if there were enough talks submitted. Currently, there are already 7 talks submitted to "Runtime and cloud" targeted to ACS. Unfortunately, the CPF will last until 23:59 UTC on April 15, 2024; therefore, we have a short time to try to make that happen. Thus, if you are interested, we invite you to submit a CloudStack talk to the track "Runtime and cloud" at COCNA 2024[1]. Best regards, Daniel Salvador (gutoveronezi) [1] https://communityovercode.org/call-for-presentations/
Re: [I] Installing v0.5.0 gives error about unexpected hash [cloudstack-terraform-provider]
rohityadavcloud commented on issue #109: URL: https://github.com/apache/cloudstack-terraform-provider/issues/109#issuecomment-2067557335 Hi @CodeBleu sure feel free to re-open the issue. Can you try the same with terraform, in a docker container or a new VM? -- 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-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Update hash generation [cloudstack-terraform-provider]
rohityadavcloud merged PR #108: URL: https://github.com/apache/cloudstack-terraform-provider/pull/108 -- 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-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump golang.org/x/net from 0.0.0-20210805182204-aaa1db679c0d to 0.23.0 [cloudstack-terraform-provider]
dependabot[bot] commented on PR #111: URL: https://github.com/apache/cloudstack-terraform-provider/pull/111#issuecomment-2067557680 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump golang.org/x/net from 0.0.0-20210805182204-aaa1db679c0d to 0.23.0 [cloudstack-terraform-provider]
rohityadavcloud closed pull request #111: Bump golang.org/x/net from 0.0.0-20210805182204-aaa1db679c0d to 0.23.0 URL: https://github.com/apache/cloudstack-terraform-provider/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-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
