Skip to content
This repository was archived by the owner on Jan 30, 2020. It is now read-only.

Conversation

@jipperinbham
Copy link
Contributor

expose username and password as options for configuration to etcd endpoints

Fixes #1505

#### Using systemd Drop-Ins

```ini
[Service]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if you provide etcd_servers in examples below, put it here too. if you use https protocol, probably it worth to mention TLS keypairs described above.

@kayrus
Copy link
Contributor

kayrus commented Mar 15, 2016

@jipperinbham nice patch. could you also add extra info into Documentation/using-the-client.md?

@jipperinbham
Copy link
Contributor Author

@kayrus I made some additions to both Documentation/deployment-and-configuration.md and Documentation/using-the-client.md but let me know if the wording needs some adjustments.

I also ditched the if guards for Username and Password since the etcd client performs the same logic.

Environment="FLEET_ETCD_PASSWORD=coreos"
```

#### Using CoreOS Cloud Config
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jonboulle thanks for the heads up, I've submitted coreos/coreos-cloudinit#418

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be nice, if the documentation could also show how to use TLS authentication by default.

Thanks!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kayrus
Copy link
Contributor

kayrus commented Mar 31, 2016

@jonboulle should we create tests for this PR? otherwise let's just close #1447 issue and merge this PR.


globalFlagset.StringVar(&globalFlags.EtcdUsername, "etcd-username", "", "Username used to authenticate with etcd")
globalFlagset.StringVar(&globalFlags.EtcdPassword, "etcd-password", "", "Password used to authenticate with etcd")

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the documentation and the patch, but honestly I don't like the fact that username and password will show up on the cmdline where every process will just grab them... so could you please make just a one option where it reads the input from the config file ?

Thank you!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm do we have any other config variables that can be set from the config file but not CLI?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm, I'm not aware of any other variables that works like that!
but if I'm not mixing things this code touches the old etcd API which was deprecated right ? and in that case do we need to expose these information ? it will be world readable and having a vulnerable node will just expose the whole cluster...

In fleetd it's fine, since it is retrieved from the configuration file. IMO the only thing to do if you are writing systemd drop-ins with such content is perhaps to make sure how you store that information.

@crawford
Copy link
Contributor

Bump

@dongsupark
Copy link

Thanks for the bump. Overall it looks ok to me, but I also share with @tixxdz concerns about exposing username/password via cmdline. But actually I don't have strong opinions.

@jipperinbham
Copy link
Contributor Author

@dongsupark @tixxdz I removed etcd username and password options from fleetctl


### Using etcd Authentication

If your `etcd` cluster is configured with authentication enabled, use the `--etcd-username` and `--etc-password` flags to provide credentials to the command-line tool.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One minor nit: is this description still valid, given that the options are now removed from fleetctl?

@dongsupark
Copy link

@jipperinbham BTW this PR needs a rebase. As soon as a minor document change gets done, I'd be ready to merge it. Functional test failed, but I suppose that's just an occasional failure, which has nothing to do with this PR.

@dongsupark dongsupark force-pushed the master branch 2 times, most recently from 14580b0 to 63b20dc Compare June 22, 2016 10:22
@dongsupark dongsupark force-pushed the master branch 3 times, most recently from 23d4b13 to 6fb1256 Compare July 1, 2016 11:07
@dongsupark dongsupark force-pushed the master branch 2 times, most recently from 54409ab to a1a21b8 Compare July 8, 2016 11:38
@dongsupark
Copy link

@jipperinbham gentle ping.
If you don't have much time, I could rebase it by myself to merge it.

@dongsupark
Copy link

Closed in favor of #1630. Thanks.

@dongsupark dongsupark closed this Jul 13, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants