#631: remove -D on server add #448
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "ammaratef45/abra:removeDomainCheck"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
toolshed/organising#631
Nice one @ammaratef45! That's a great start.
There are however still some places where domain checks are carried out. See
EnsureDomainsResolveSameIPv4
also underabra app deploy ...
which relates to toolshed/organising#631 (comment).I think taking a scan of
pkg/dns/...
, seeing what is in there in terms of functions and where those get called will give you an overview of the logic. I think the idea is that domain checking happens once on theabra server add
and from then on in, it's "up to you"./cc @p4u1 @fauno
@ -122,3 +119,1 @@
of your ~/.ssh/config. Checks for a valid online domain will be skipped:
abra server add -D example`,
`,
Might seem like a nitpick but this "`" needs to be on the same line as the
"default"
or else a newline is created in the help output ofabra
which is inconsistent with the rest of the commands as far as I remember 🙃Ah, mia culpa
I thought the idea is that domain checking results only in a warning for
server add
but since apps can have domains that are not subdomains of the server then we need to keep domain checking for them?Or do we want to have this as a warning in all of the cases? I could just remove the
-D
parameterinternal/cli
and go chase everywhere where an error shows up if that's the goal@ammaratef45 I understood from toolshed/organising#631 (comment) that perhaps the additional domain checks on deploy were also a hindrance? @fauno will hopefully weigh in on this shortly.
We can also just merge as-is as @p4u1 is suggesting (this change stands on its own and is good anyway pending coop-cloud/abra#448 (comment))! Feel free to click the big green button!
😢