Draft: Doc update

Minor updates, as well as DNS updates.

added 1 commit

• bf24f9df - Update c_development.md

Compare with previous version

added 1 commit

• a491bb73 - Update c_development.md

Compare with previous version

added 1 commit

• 73acd34d - Update c_development.md

Compare with previous version

added 1 commit

• e7ea92df - Update c_development.md

Compare with previous version

added 1 commit

• 15ddfeb8 - Update c_development.md

Compare with previous version

added 1 commit

• 077868f1 - Update c_development.md

Compare with previous version

approved this merge request

This is blocked by @kevin.wilder 's fix in !132 (closed) that adds the new .mil domain.

in the process of cleaning up old MRs... is this still needed and/or up to date @jasonkrause?

added kinddocs statusdoing labels

added 2 commits

• 92d0e982 - Squash commits.
• 2e15bb23 - Merge branch 'doc-update' of https://repo1.dso.mil/platform-one/big-bang/bigbang into doc-update

Compare with previous version

added 161 commits

• 2e15bb23...47688698 - 158 commits from branch master
• 5af2e598 - Squashing commits.
• 1613a30c - Merge branch 'doc-update'
• 324fbc35 - Merge branch 'doc-update' of https://repo1.dso.mil/platform-one/big-bang/bigbang into doc-update

Compare with previous version

@joshwolf I think this worked, let me know if it did now.

@jasonkrause it looks like there are merge commits that have been committed. Please resolve those

Should be resolved now.

added 2 commits

• 0e6b5082 - docs: c_dev updates
• 5bd524a6 - Merge branch 'doc-update' of https://repo1.dso.mil/platform-one/big-bang/bigbang into doc-update

Compare with previous version

added 1 commit

• 3168fab6 - Fixing merge conflicts, merge messages,style

Compare with previous version

The deployment steps from line 280 to 389 are out-of-date, wrong, and don't work anymore.
Specifically the steps that tell you to create the bigbang namespace and deploy secrets before "helm upgrade -i". That does not work and will throw errors because the bigbang namespace already exists. Instead you have to supply values to bigbang helm chart for the ingress cert and private registry. Bigbang will create the secrets.

Should it be corrected on this MR?

I'm good either way. ¯\＿(ツ)＿/¯

marked this merge request as draft

Moving this back to draft. I have issue https://repo1.dso.mil/platform-one/big-bang/bigbang/-/issues/95 to move the developer onboarding documentation in confluence to Gitlab. The plan is to move it to the Gitlab Wiki instead of markdown file in the actual bigbang code. As part of that issue I will be clobbering this file and moving the content to the wiki.

That works for me.

Once that is complete, we can iterate on that documentation faster.

OBE

closed