#4425 add initial private vars to ansible for taskotron-dev
Closed: Fixed Opened by tflink.

taskotron-dev will need the following private variables:

  • buildbot_user:
  • buildbot_pw:
  • buildmaster_db_user:
  • buildmaster_db_pw:
  • fakefedorainfra_secret_key:
  • python -c 'import os; print os.urandom(24).encode('string_escape')'

That was supposed to be:

python -c "import os; print os.urandom(24).encode('string_escape')"

Done and added. Let us know if you need anything further.

After discussing variable names in different environments, it makes sense to have dev-specific variables for most of these. We'll be using the same variables for production, so they can be copied (except fakefedorainfra_secret_key, that won't be used in production)

So the list would become:

  • dev_buildbot_user:
  • dev_buildbot_pw:
  • dev_buildmaster_db_user:
  • dev_buildmaster_db_password:
  • dev_fakefedorainfra_secret_key:
  • dev_fakefedorainfra_db_user:
  • dev_fakefedorainfra_db_pw:

note the two fakefedorainfra_db values that I forgot to include earlier.

bah, I forgot a variable:

  • dev_buildmaster_db_name:

Three more for the taskotron clients that I wasn't thinking about:

  • dev_buildslave_user:
  • dev_buildslave_password:
  • dev_taskotron_fas_password:

Note that we're not using fas with taskotron yet - I still need to request the account and that will only be used with production. It's just used with fake_fedorainfra which doesn't check credentials so anything random will work as long as the variable exists.

Done

Note that there are other application integrating with FAS (pkgdb2 for one), should we share these credentials?

Sorry for all the updates, stg and prod should be smoother.

Please add:

  • dev_resultsdb_db_password:
  • dev_resultsdb_secret_key:

For the sake of maintaining sanity, could the following variable names be changed?

  • dev_buildbot_pw to dev_buildbot_password
  • dev_fakefedorainfra_db_pw to dev_fakefedorainfra_db_password

Variables added

Variables renamed

:)

Metadata