@decidim/product I've some concerns about this implementation:

• some Decidim instances, as Decidim Barcelona, are deployed to Heroku. This service uses ephemeral storage, meaning that all created files will be lost on each deploy. So, creating the files with the task seems a bit problematic, as we can't upload the private key to the repository nor create it directly on the server on those cases. That's why I've decided to print the keys on the screen and explain different options in the documentation.

• as @tramuntanal points here, secure public keys are multiline and too lengthy to be used as parameters for rake tasks, even when it's possible. I can think of three options here:
  a. keep it as it is now, using quotes to call the add_authority task:

  $ export PK="-----BEGIN PUBLIC KEY-----
  MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEA32d9tY44lfV6OdanXQ4B
  102oYFEYMouZUDHquD5yTNZZkTYJ71u9VCHtVf83rW+YUj8NZFtoCeo/g9TUwmKf
  nUl362MeNlrpbTUU2yD3rJjt5JDme4+gtFPjTneubJEOwwHBKJpDNqZB+HmxNqbz
  3nn4EoBqv8tSKFon8Mk1Nsj9aPW3jpHnVCjWUJ8wtB321TgYW2GMDv8aOkOZ/M7p
  z4pFk49Skp24knITeeKdzB2VvcRhEdAf8Lp5Jqtoh9za40Ky0AvPx/Ueh42xH9t+
  P9hfQFX5joSlCKMAPe1Xyji2gxiwWTBu60mOL7PbThiDxrOZxSVhhN21A4IrDfIN
  T2PJCDtYZUyqu6xYISPg6i3teXZrPWT4wWVcJ/dPEXJwSomuFpK7AZ07uhwSwLPw
  pZc/yUxDq3xNfyVCRfu9UoCvrKwKMK7BrXPzM6ljtD9KzjhqbXb1q+JQXDp6uxIH
  FV8TXJSZS7o2tU9G0AoXiKRIOS1t6IG19YhC6Yqn5raPjRlVO//suJS+WAV+j3tU
  SHFOHWo6HYXcS6WRHItkudXjwnyIhW06Zs+KuMKXQQmEkytcFi562pwvUH7kvAZ2
  8G0TR5G5wgRbrGQzM4WyMuemWbcFpG6RqwboffHNCkxSetDHY9WOF3EQ0pKqzaJB
  XbnNp1nB7AHiy2yxCQznpUMCAwEAAQ==
  -----END PUBLIC KEY-----"
  
  $ bin/rails "client:add_authority[Authority name, $PK]"

  b. dump the public key to a file and use it to send it to the Bulletin Board administrator, as @tramuntanal suggested
  c. add it to the graphql and change the Bulletin Board task to fetch all the Decidim instance from the graphql response, only needing the graphql endpoint, something like this:

  

  I like this solution as it is pretty straightforward for administrators, but I'm not very convinced about adding a GraphQL client to the BB and adding a dependency to Decidim, which we currently don't have - but it may be needed in the future anyway.

• As shown in the PR screenshots part, I've added a warning message to warn the administrators that the Elections module can't be used without a configured BB. This alert will appear on every visit to the elections list page until the identification keys are generated and the BB settings are set. I don't know if think that it's ok or if this could be too annoying for administrators.

That's all. As you can see, in this PR I've decided to implement the simplest approach to be able to iterate over it until we find the best solution for each concern.

I have to contradict myself but taking into account environments like Heroku that have ephemeral file systems it may be best to keep with the current implementation and pass the public key as a task parameter

@leio10 I've reformated your answer (by giving a numbered alphabetical list), so it's easier to follow/discuss.

What I was thinking initially regarding the key with the add_authority task is to have something like the one you have in ssh (ie .ssh/id_rsa.pub), that'd be less error-prone for commands IMHO.

Also in the future, after we have the first working implementation, we should make a step by step tutorial with examples of format, as this could be an issue. For instance in your c. example there are newline escape sequences (\n)

@leio10 what's the state of this PR?

@andreslucena I've addressed your comments. Regarding the link you asked to add in the warning message, it was shown inside a callout, that wasn't prepared to show links. So, I've added some styling for that. You can check it here.

@decidim/core this was approved by Product and is ready to be reviewed