Riyadh Al Nur

@thomasmerz i won't have time to look into this anytime soon. Please feel free to contribute a PR to add this feature.

Any specifics you can point me to on what I can add?

if we're looking for more people to help out, I'd be interested in being part of the team

Cool. Didn't know that. Setting the npm config will do it then. Don't think an issue is necessary in that case.

Right, but `np` isn't explicitly committing anything is it? After bumping version, if `np` commits the changes itself, then yes, signing that commit would come in handy.

https://github.com/npm/npm/issues/12696

```shell === RUN TestDNSProviders/dnscontrol-gcloud.com/12:complex_TXT:TXT_with_0-octel_string integration_test.go:220: CREATE TXT foo1.dnscontrol-gcloud.com "" ttl=300 integration_test.go:239: Expected 0 corrections on second run, but found 1. integration_test.go:241: UNEXPECTED #0: MODIFY TXT foo1.dnscontrol-gcloud.com: ("\"\"" ttl=300) -> (""...

The parser under `namedotcom` along with the `SetTargetTXTs()` method works for `GCLOUD` as well. I would opt for moving the parser under the `txtutil` package. If we're on the same...

Integration tests for `GCLOUD` run successfully 

Hey @tlimoncelli, I asked @asn-iac to open this as an actionable ticket for the TODO from the original support in #2481. We can re-open in case someone's interested in picking...