deis-admin
commented
7 years ago From @nathansamson on June 16, 2015 9:19
Hi,
Why I support this feature (in a broader way actually), it is exactly the other way around. The CI system (and ONLY the CI system in principle) should know the private key, while deis would need the public key.
In general I am intrested in more fine-grained ACL's to apps, specifically I am intrested in following options
- (As this use case): a (pseude)-user that can do deployments
- A user to manage domains / certs
- An admin that can do everything.
Reason I am intrested in second bullet point is that I have a website where people (in the future) should be able to subscribe to a SaaS system, and choose their own domain name attached to it. At that point a very restricted user should be able to access the DEIS API, and add domains to the app.
Nathan
On Tue, Jun 16, 2015 at 10:17 AM, Scott Robertson notifications@github.com wrote:
Hey,
It would be quite cool if we could add deployment keys to a project. The work around right now is to create a deployment user, but that is a bit cumbersome.
When adding deployment keys, we should have the ability to supply our own, or have deis generate a keypair automatically (and return the public key so we can add it to CI).
— Reply to this email directly or view it on GitHub https://github.com/deis/deis/issues/3875.
Cryptophobia
From @scottrobertson on June 16, 2015 8:17
Hey,
It would be quite cool if we could add deployment keys to a project. The work around right now is to create a deployment user, but that is a bit cumbersome.
When adding deployment keys, we should have the ability to supply our own, or have deis generate a keypair automatically (and return the public key so we can add it to CI).
Copied from original issue: deis/deis#3875