Move aws-env* to parameter store about bugzilla-customisation HOT 16 CLOSED

Once again I'm a bit lost and I'll more information and context on where/when/how this should be done.
I'm trying to configure the dashboard in the prod environment and I'm scratching my head on how I can efficiently convert this from what looks like a vanilla BZ installation into a the latest version of the BZFE.

The first issue I'm running into is I don't know where to find the password for the initial user created in ([email protected]). I could work around that probably but this is just to illustrate how lost I fell right now...
Apologies for what might appear to be a very dumb question...

from bugzilla-customisation.

I think your query is about SQL, and not about the secrets in the environment, right?

The production SQL was primed IIUC by checksetup.pl.

I assumed you would basically overwrite the SQL in the production database at this point. I.e. not use the Web interface to setup anything regarding the database.

from bugzilla-customisation.

I could do that
That was my initial impulse actually but I just wanted to make sure that this was the right thing to do...
I was actually wondering why you did not use the sql dump from the Bugzilla configuration folder when you re-built the production environment...

from bugzilla-customisation.

This also leads to a related question: "if the DB is a vanilla DB, which other customization have been omitted there? Skins? Custom?"

from bugzilla-customisation.

"I assumed you would basically overwrite the SQL in the production database at this point."
just for the records, I just did that right now...

from bugzilla-customisation.

The running production as I left it over the weekend basically only has the initial localconfig/params.json. Nothing from https://github.com/unee-t/bugzilla-customisation/tree/master/sql.

From there I think skins and custom are setup.

from bugzilla-customisation.

OK thanks for the clarification.
I'll do the params.json manually in the back end (much faster for now) and then we'll be able to lift the params.json file once I understand where I need to log in to execute the command
docker cp customisation_bugzilla_1:/opt/bugzilla-5.0.3/data/params.json /tmp/params.json

from bugzilla-customisation.

from bugzilla-customisation.

prod environment configured BEFORE migration.
parameters have been modified. The file params.json should be OK (I still need to understand how I can copy it).
email tested and seem to work as intended.
Next step will be to migrate the LMB users and cases from the LMB internal tool into Unee-T

from bugzilla-customisation.

What's your docker ps output?

from bugzilla-customisation.

from bugzilla-customisation.

Aren't you missing the make up step to get your Docker containers up and running?

from bugzilla-customisation.

I do miss it...
for some reason I took that installation down and forgot to build it up again 😊

Still have the same error though

from bugzilla-customisation.

Docker has inconsistent naming between versions. I can see your running container is called "bugzillacustomisation_bugzilla_1", so you need to adjust the copy command accordingly.

from bugzilla-customisation.

cool that did it thanks!

from bugzilla-customisation.

This is done https://s.natalian.org/2017-11-10/1510284612_2558x1406.png

from bugzilla-customisation.