-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add new secret ONE_TRUST_SCRIPT_DOMAIN
#523
Comments
lsloan
added a commit
to lsloan/rohq
that referenced
this issue
Jul 2, 2024
lsloan
added a commit
to lsloan/rohq
that referenced
this issue
Jul 2, 2024
As I noted in the PR, we also need to add back in the code that makes use of this value. We can cherry-pick it out of a78f282 or re-do it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Make a new environment variable available to the application,
ONE_TRUST_SCRIPT_DOMAIN
.It requires two small changes:
In
service/base/kustomization.yaml
, add the line…This change needs to be committed to this GitHub repo.
Then create the file service/base/secret/ONE_TRUST_SCRIPT_DOMAIN which contains a single line, the value for the key…
The file was put in that location based on the premise that the same value would be used in all environments, prod, test, and dev. If instead the environments will have unique values for this key, it can be added to the directories for each one.
This change needs to be committed to the secret archives in Dropbox.
When running the Kustomize process as shown in README.md, it produces a long output containing the base64-encoded secrets and other resources. The value was found and decoded to verify it was correct.
Using the full command to apply the output to ROSA, the ROSA web UI was used to find the secret, see its value, and confirmed it is correct.
As noted above, the two changes described above need to be committed in two places. The first step must be committed to the GitHub repo. The second step must be saved in an updated secrets file in Dropbox.
The text was updated successfully, but these errors were encountered: