domain2find4delete

dragonxi

How to find an extra domain to delete it ?
(1) Status
202 domains
100 applications
100 site routes
i.e ** two extra domains **
could be xxxxxxxx.de i.e .dev typo error

(2) challenges to find two extra erroneous domains among 202 :
(a) no *.de neither *.ap option in search
i.e opalstack find does not offer . type search
(b) erroneous extra domain may not get listed
i.e opalstack server may list only ok domains
(c) erroneous extra domain will pop up as
a candidate domain for new site routes
(d) one must be sure which domain is extra
i.e to delete only those two which have not be configured to any working site route

(3)
Is there a way to search orphan domains,
those not attached to any site route using

opalstack control panel GUI ?
using Linux commands as shell user ?

(4) The following is just feedback/wish list:
(a) having a program counting site group, domain and application totals would be useful

or is there any software/command doing it ?
(b) having a find service/tool such as
*.de to find domains which should be *.dev
"orphan" search to find domains which have not configured for any site route
or is there already tool/command doing it ?

Thanks for your excellent support due to which we have 100 site routes and application with 200 domains working, WELL DONE !

dragonxi

Can support guys see what are those two ectra domains we need to delete ?

sean

dragonxi Search seems to work fine, I checked domains in your dashboard like this:

Searched for ".de" and the list filtered to show all of your ".dev" domains. I scrolled through the list and did not see any ".de" typos.
Searched for ".ap" and the list filtered to show all of your ".app" domains. I scrolled through the list and did not see any ".ap" typos.

We don't have a pre-made tool to show you orphan domains but you can do that with a series of API calls like this:

export TOKEN=xxxxxxx # replace with your token from https://my.opalstack.com/tokens
curl --silent --header "Content-Type:application/json" --header "Authorization: Token $TOKEN"  https://my.opalstack.com/api/v0/domain/list/ | jq -r '.domains | .[] | .id' > alldomains
for site in `curl --silent --header "Content-Type:application/json" --header "Authorization: Token $TOKEN"  https://my.opalstack.com/api/v0/site/list/ | jq -r '.sites | .[] | .id'`; do curl --silent --header "Content-Type:application/json" --header "Authorization: Token $TOKEN"  https://my.opalstack.com/api/v0/site/read/$site | jq -r '.domains | .[] | .id'; done | sort | uniq > domains_in_use
grep -F -f domains_in_use -v alldomains > unused_domains
for domain in `cat unused_domains`; do curl --silent --header "Content-Type:application/json" --header "Authorization: Token $TOKEN"  https://my.opalstack.com/api/v0/domain/read/$domain| jq -r '.name'; done

aa11

sean We don't have a pre-made tool to show you orphan domains but you can do that with a series of API calls like this:

That's clever @sean!

Slight variable name correction needed to the code:

Before: $TOK
After: $TOKEN

Or:

Before: export TOKEN=
After: export TOK=

Without this you receive jq: error (at <stdin>:0): Cannot iterate over null (null) errors.

(I'll modify this comment after that update.)

UPDATE (2020-12-02): Fixed

dragonxi

sean (1) orphan domain is senseit.de
(2) senseit_de was not displayed when I listed all domains - that's why I did not find it
(3) which command to use to delete it ?
(4) my tests proved that the server did propose sense_de
as one alternative when I crested a new test Site Group, thast's why it would be useful to delete it

(5) THANK having spent your busy time investigating this issue, /"devil is sometimes in details"/

sean

aa11 Sorry about that, I've corrected my example.

sean

dragonxi If you go to https://my.opalstack.com/domains/ and search for senseit.de (be sure to press enter in the search box) then the list will filter and you'll see the domain there. You can then delete it.

Instructions for deleting a domain are in our user guide: Deleting Domains

dragonxi

(1) found it
(2) deleted it.
(3) statistics (Site Routes, Domains...) ok now