Closed slifty closed 5 years ago
Pushed directly to master due to the sensitive nature -- we may want to actually squash this all the way back to the original commit to wipe the history, though that would mean a force push to master which I'm worried might cause pain and suffering.
The password has to be changed either way since it was out there and may have been scraped.
Can we wipe out the history and remove cache as well. Force push to master to remove all the information including elastic instance details is worth doing it . Can you please help.
We can actually git pull locally all the changes done to this repo and delete this repo completely and then create a new repo and check in all the changes there.
Absolutely -- will do first thing tomorrow morning.
Deleting this issue.
The
config/properties.env
contains sensitive information.We need to: