Wildcard Sites?
Comments
-
Adding my +1 on this as well
0 -
+1 - we use Netlify deploy previews and it's arduous to always manually look up the credentials.
0 -
+1 to wildcard support
I also have the need for those, with preview deploys which we generate URLs in the format of
random.staticpart.com0 -
I want to bump this and add that I have similar use case at both the FQDN/subdomain level as eman mentioned, as well as logins I have stored by private IP address for logins internally within my corporate network like dig mentioned. Having to add dozens or even into triple digits in a singular login as additional URLs not the desired way I would like to do it, especially if we break out some of those devices/addresses with a different password at some point int he future and now have to go find/rip out that address from the long list of additional URLs in a sign-in item to add a new one. Please have a way to add a subnet or wildcard feature! :)
0 -
+1, prevents 1pass suggestions for vercel preview deployments (ours look like
https://<repo>-<branch>-<org>.vercel.app)wildcard subdomain seems like a needed feature to use 1pass with a lot of PaaS offerings (vercel, heroku, render.com, etc)
https://vercel.com/docs/concepts/deployments/preview-deployments
0 -
Also +1 to wildcard support.
This seems to be a fairly commonly requested feature when searching around for solutions, curious if there's any particular reason why this is not supported (security concerns? scoping / priority?)
This is a major pain-point for us, and open to any workarounds if possible.
0 -
+1 for this too!
0 -
+1 for wildcard URL support.. But I see this has been requested since early 2017. I don't think they will ever add it.
1 -
+1 And I don't see this as an edge case.
1 -
+1 for wildcard URL support!
1 -
+1 here as well
We have a similar usecase to the one on netlify, using it for dev/preview domains.
1 -
+1 for me and our whole team.
We use preview branches on Vercel alot and would benefit a whole lot from this feature.
0
