Steps taken:
$ make docker-compose-test
Create /root/.config/zanata.ini (Obtained from https://translate.engineering.redhat.com/dashboard/settings/client)
Update .pot files:
$ make pot
$ make languages
Push to Zanata:
python tools/scripts/manage_translations.py push --both --lang es
* Modify instance model to container a version number for the node
* Update that version number during the heartbeat
* If during a heartbeat any of the nodes are of a newer version then
shutdown the current node.
The idea behind this is that if all nodes were upgraded at the same
time then at the moment of the healthcheck they should all be at the
newer version. Otherwise we put the system in a state where it can
receive the upgrade but stay down until that happens. During setup
playbook run the services will be fully restarted.
Applies to both single-select and multi-select type questions.
UI sends choices in the form of text with line breaks
separating the options.
Customer complained about empty string erronously sent by
the UI being passed to playbook, which is a component of this.
Newer ansible versions don't allow with_items to reference undefined
variables so we'll provide a default.
We'll also update some conditionals to deal with naming requirements
changes on insights api endpoints
These macros were intended to pull the version and release from a python file if they werent passed in with --define, but /usr/bin/python is not available at this point in the build process. I'm not sure when or if this ever worked. Perhaps before we were using mock.
This approach also works for our Brew builds, as we cannot specify a macro value at build time.
* release_3.1.2: (149 commits)
updating changelog for 3.1.2
Add back SRC_ONLY_PKGS
Fix ubuntu 14 restart service list pt 2
Make sure the insight playbook fetch doesn't quote user and pass
Add requirements/vendor to gitignore
Conditionally install from local python dependencies in spec file
Remove requirements/vendor on make clean.
Update brew-srpm target to generate local requirements files
Get offline pip installs working
Add clean-dist target
Navigate back to the jobDetails state when the user clicks outside the host event modal.
Don't use jinja quote filter on insights username or password
fix legacy standard out
Fixed permissions typo
add test, restore old behavior in api test
create _survey_element_validation and use it for updating extra_vars
Do not set the default if the field was not passed in to kwargs_extra_vars
Remove log aggregator port required mark.
Modify according to review feedback.
Host Event json should be read-only
...
This looks pretty hairy, but essentially it's just re-invoking `pip download` with `--no-deps` so that I can record the name of the local archives that are created.
I had to pull the git urls out of the main requirements files because in order to install offline (--no-index), we need pip to install from local package archives rather than cloning repo.
The weird `cat` thing going on in the Makefile is because we need to install everything as part of a single `pip install` transaction. Without this, installing only requirements_git.txt will result in dependencies getting unintentionally updated.
This fixes an issue where a user was trying to use an exclamation mark
in the password. Historically we've used the quote filter but more and
more we're seeing conflicts with special characters
Shane McDonald
Bill Nottingham
Michael Abashian
Matthew Jones
Aaron Tan
Alan Rominger
Matthew Jones
Michael Abashian
jlmitch5
Wayne Witzel III
Ryan Petrello
Ryan Petrello