ipfs-shipyard / dnslink-cloudflare Goto Github PK

Support and document cloudflare auth tokens.

I think you probably need Zone > Zone > Read and Zone > DNS > Edit permissions FYI.
Also based on my testing you need to not restrict the token to one zone.

I have web3 IPFS gateway subcription. when I create an IPFS gateway it will create DNS records as well (hostname and DNSLink), I can't update the DNSLink record.

Should I check the API token permisssion?
or
this binary does not have this funtionaly to edit DNSLink created by IPFS gateway?

Thanks

Could we get a new build with the dependency / security updates?

Thanks!

Should we move this package to ipfs org. We have there:

• dnslink-dnsimple
• dnslink-deploy (DigitalOcean)

?

Also, I should add someone else as a collaborator on NPM.

/cc @olizilla @lidel

Hello! I could not find 1 example of the command

After creating the API token for read all zone and edit sepcific zone. I am receiving error HTTPError: Response code 403 (Forbidden)

Below is the command
CF_API_TOKEN="mytoken" npx dnslink-cloudflare -d myDomain -l fromlocal -r test

• I own the domain which have a txt record with name test. I want to change the content of the test record to fromlocal through this binary, then I will put this command in the CI/CD pipeline.

If you have more than 20 records then this probably won't find the dnslink TXT record. This should perform pagination to check all records.

Right now, dnslink-cloudflare requires zone:read for all zones, and dns:edit for one specific zone

I cant remember the first permission being required in previous versions of this library, and the change resulted in me debugging crashing deployments (via ipfs-deploy), please describe (in the readme) which permissions are required for the API token, for the library to function.