We are running rstudio connect in a docker container. We are setting the bitbucket private repo in the rstudio-connect.gcfg file with the Pat encrypted password.
The encryption is done by /opt/rstudio-connect/bin/rscadmin configure --encrypt-config-value. But the authentication keeps failing when we want to publish from this bitbucket account.
Also when we execute the opt/rstudio-connect/bin/rscadmin configure --encrypt-config-value twice in a row. We get different strings, Is this normal ?
What is the best way to set this up in a docker container ?
You do get different strings - and that is normal because we add a salt/hash. Otherwise it is possible to "brute force" a value by guessing and comparing hashes This is pretty standard in encryption-land, but can make "checking / validating a value" challenging.
If that is what you are looking for, there is unfortunately no answer today, although I will provide feedback to the product engineers that a way to "check a value" would be valuable. Especially because idempotency often requires such things.
Doing this workflow in a docker container is challenging because of the idempotency restriction I mentioned above. However, we have seen users accomplish this task by using an entrypoint script, an "init container" / container that runs before other things, etc.
If chatting through options would be helpful, we are happy to do so either here, in our support queue, or through your account representative!
This is pretty standard in encryption-land, but can make "checking / validating a value" challenging.