chown the definitions to the rabbit user after our script edits them

[MoralCode]

Description

• This makes a small adjustment to our container build order for rabbitmq such that the permissions are changed after our script that adjusts rabbit config is run

This PR fixes #3734

Notes for Reviewers

Signed commits

• Yes, I signed my commits.

[sgoggins]

If the issue is that update_config.py cannot write to definitions.json ... just trying to wrap my head around whether or not this "should" work.

Given this error:

PermissionError: [Errno 13] Permission denied: '/etc/rabbitmq/definitions.json'
Error: building at STEP "RUN exec python3 update_config.py": while running runtime: exit status 

it would seem like /etc/rabbitmq, if owned by the rabbitmq user, would then allow for the definitions.json file to be written.

I have not tested this, just thinking about the logic I see, @MoralCode .

[sgoggins]

It would again seem to me that changing permissions on a file that can't be written won't work ... but this may be something I don't understand.

[MoralCode]

What are you asking?

[MoralCode]

If the file can't be written due to permissions issues adjusting the permissions seems like it would help

[sgoggins]

Does the file already exist though?

[MoralCode]

Yeah, it's in the same folder as the Dockerfile. I think one of the previous Dockerfile steps is that we copy the file into the container before we run this script to make the final adjustments to it.

The problem here is essentially that if we run this chown line before we run the script that changes the file, we change the permissions such that the script can no longer edit the file, causing the crash.

I still need to run some builds with this new ordering of the build steps to make sure that the problem goes away, but I'm pretty confident that this is what's happening.

[MoralCode]

can confirm this fixes the build on my machine. will run it while testing other stuff to make sure rabbit behavior is unchanged as anticipated