-
Notifications
You must be signed in to change notification settings - Fork 180
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
Fix Shared RP Documentation #3812
base: master
Are you sure you want to change the base?
Conversation
export DATABASE_NAME="\$AZURE_PREFIX" | ||
export RESOURCEGROUP='$RESOURCEGROUP_PREFIX-\$LOCATION' | ||
export PROXY_HOSTNAME='vm0.$PROXY_DOMAIN_NAME_LABEL.\$LOCATION.cloudapp.azure.com' | ||
export DATABASE_NAME='\$AZURE_PREFIX' | ||
export RP_MODE='development' | ||
export PULL_SECRET='$PULL_SECRET' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am pretty confident that USER_PULL_SECRET is missing here, but IDK how to create/find it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does make secrets get you the pull secret?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pull secret mentioned here only consists for tokens for prod and int svc acr and not to say other registries like redhat or quay, these can provided to cluster during install or at later stages, RP doesn't need them and not a blocker for cluster creation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does make secrets get you the pull secret?
It does, but I am concerned about the USER_PULL_SECRET which is missing in the docs and exists in practice when you run SECRET_SA_ACCOUNT_NAME=rharosecretsdev make secrets
.
/azp run ci, |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think these changes do look correct. I'll ask for one more person to confirm. Please see my comment on Pull Secret and let me know if you get that solved.
export DATABASE_NAME="\$AZURE_PREFIX" | ||
export RESOURCEGROUP='$RESOURCEGROUP_PREFIX-\$LOCATION' | ||
export PROXY_HOSTNAME='vm0.$PROXY_DOMAIN_NAME_LABEL.\$LOCATION.cloudapp.azure.com' | ||
export DATABASE_NAME='\$AZURE_PREFIX' | ||
export RP_MODE='development' | ||
export PULL_SECRET='$PULL_SECRET' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does make secrets get you the pull secret?
/azp run e2e |
Azure Pipelines successfully started running 1 pipeline(s). |
d1b3165
/azp run ci,e2e |
Azure Pipelines successfully started running 2 pipeline(s). |
/azp run e2e |
Azure Pipelines successfully started running 1 pipeline(s). |
I have updated the PR according to your great tip from Slack on using single quotes.
I have addressed that in the last commit. Let me know if that's ok and if can we merge it now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. One small spelling error.
/azp run ci,e2e |
Azure Pipelines successfully started running 2 pipeline(s). |
Please rebase pull request. |
PARENT_DOMAIN_RESOURCEGROUP was missing an export
Stay consistent and all the env vars are set using single quotes instead of double
The value of ADMIN_OBJECT_ID is used twice before it was declared as env variable. Now it will be declared beforehand
Due to indentation levels the page was rendered wrongly
Move the non-required procedures at the end under a new seciton and connect the certs creation with the certs rotation
Stay consistent and all the env vars are set using double quotes instead of single. When single quotes on the exported variable includes escaped $ then you can create a literal string ''
64bc873
acb1b1d
to
64bc873
Compare
Which issue this PR addresses:
It fixes the shared RP documentation.
What this PR does / why we need it:
env
file (missing export, and consistent string declaration)Test plan for issue:
Not required but the documentation will be used in a new planned automation
Is there any documentation that needs to be updated for this PR?
Yes
How do you know this will function as expected in production?