chore: fix npm install, try and fix npm run build

Author: esacteksab

docs/infrasec/ansible/ansible-primer.md

@@ -5,14 +5,14 @@ remote-execution tool originally designed to orchestrate a wider environment, it
 with things like Packer, which is where you are most likely to see it in a Truss environment.
 
 This primer is not intended to replace the official documentation for Ansible, which can be found at
-<https://docs.ansible.com/ansible/latest/index.html>. It is only intended to provide a high-level overview and give you
+[https://docs.ansible.com/ansible/latest/index.html](https://docs.ansible.com/ansible/latest/index.html). It is only intended to provide a high-level overview and give you
 an idea where to find more detailed resources.
 
 ## Setting up your environment
 
 When working with Ansible, you’ll probably want to set up a virtual environment so that you can install ansible and any
 other Python modules necessary without contaminating your system Python installation. If you’ve never done this before,
-this tutorial should help: <https://www.pythonforbeginners.com/basics/how-to-use-python-virtualenv/>. If you're an
+this tutorial should help: [https://www.pythonforbeginners.com/basics/how-to-use-python-virtualenv/](https://www.pythonforbeginners.com/basics/how-to-use-python-virtualenv/). If you're an
 experienced Python programmer and want to use `pipenv` or another alternative, that's perfectly fine too. It is
 recommended that you use Python 3 as your Python binary.
 

docs/infrasec/ansible/molecule-primer.md

@@ -7,13 +7,13 @@ experiences and resources you can use when adding testing to your own Ansible ro
 
 These resources will likely come in handy when trying to get Molecule up and running for yourself:
 
-- Molecule Official Docs: <https://molecule.readthedocs.io/en/latest/>
+- Molecule Official Docs: [https://molecule.readthedocs.io/en/latest/](https://molecule.readthedocs.io/en/latest/)
 - Testing Your Ansible Roles with Molecule (Jeff Geerling):
-  <https://www.jeffgeerling.com/blog/2018/testing-your-ansible-roles-molecule>
+  [https://www.jeffgeerling.com/blog/2018/testing-your-ansible-roles-molecule](https://www.jeffgeerling.com/blog/2018/testing-your-ansible-roles-molecule)
 - Test-driven Infrastructure Development with Ansible and Molecule (Jonas Hecht):
-  <https://blog.codecentric.de/en/2018/12/test-driven-infrastructure-ansible-molecule/>
+  [https://blog.codecentric.de/en/2018/12/test-driven-infrastructure-ansible-molecule/](https://blog.codecentric.de/en/2018/12/test-driven-infrastructure-ansible-molecule/)
 - Continuous Cloud Infrastructure With Ansible, Molecule, and TravisCI on AWS (Jonas Hecht):
-  <https://blog.codecentric.de/en/2019/01/ansible-molecule-travisci-aws/>
+  [https://blog.codecentric.de/en/2019/01/ansible-molecule-travisci-aws/](https://blog.codecentric.de/en/2019/01/ansible-molecule-travisci-aws/)
 
 ## Setup
 
@@ -46,7 +46,7 @@ for instance, and one with EC2). These commands both take a number of command li
 you’ll probably use is `--driver-name`: This tells molecule which driver to use for the scenario it is creating; by
 default this is docker, but this is where you would put ec2 or vagrant or whatever else if you wanted to test it another
 way. See the Molecule docs here for more information:
-<https://molecule.readthedocs.io/en/latest/configuration.html#driver>.
+[https://molecule.readthedocs.io/en/latest/configuration.html#driver](https://molecule.readthedocs.io/en/latest/configuration.html#driver).
 
 ## Configuration
 
@@ -56,7 +56,7 @@ specify the different components you want to use like driver, linter, verifier,
 specify the AMI, instance type, and subnet. The Molecule driver docs above have more details on what can be set here.
 
 Of special note is that for systemd-based docker images, you will need to use a few extra configuration options; the
-bottom of the docker driver docs (<https://molecule.readthedocs.io/en/latest/configuration.html#docker>) has more details.
+bottom of the docker driver docs ([https://molecule.readthedocs.io/en/latest/configuration.html#docker](https://molecule.readthedocs.io/en/latest/configuration.html#docker)) has more details.
 Since most modern Linux distributions use systemd, you’ll probably need to use this.
 
 If you have other Ansible roles your role is dependent on, be sure to specify this in the `meta/main.yml` file in your
@@ -77,7 +77,7 @@ If this works, you know that at least the Molecule parts are working right.
 ### Testing in EC2
 
 With EC2, there a couple of other steps you’ll need to take. First, you’ll have to define an EC2_REGION environment
-variable like so (this is due to the error described here: <https://github.com/ansible/molecule/issues/1570>):
+variable like so (this is due to the error described here: [https://github.com/ansible/molecule/issues/1570](https://github.com/ansible/molecule/issues/1570)):
 
 > `export EC2_REGION=”us-west-2”`
 
@@ -117,7 +117,7 @@ instances so I could poke around in them when something wasn’t working.
 By default, Molecule is not testing anything other than the accuracy of your Ansible code -- is it written right and
 does it run without generating errors. This doesn’t tell you if it’s actually doing what you want it to, though. For
 that, you’ll need to write additional tests. By default, these use Test-Infra
-(<https://testinfra.readthedocs.io/en/latest/>); you’ll put these in the `molecule/scenario_name/tests` directory. You
+([https://testinfra.readthedocs.io/en/latest/](https://testinfra.readthedocs.io/en/latest/)); you’ll put these in the `molecule/scenario_name/tests` directory. You
 should see a `test_default.py` file there already; this test is an example that just makes sure the `/etc/hosts` file
 and root user exist, which is a bare minimum for things to actually work.
 

docs/infrasec/aws/org-bootstrap.md

@@ -19,7 +19,7 @@ account. The purpose of this account is to handle root-level service
 control policies [(SCPs)](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scp.html)
 and encompass the the organizational units (OUs) underneath. If you
 need to know how to create an AWS account, please see
-<https://aws.amazon.com/premiumsupport/knowledge-center/create-and-activate-aws-account/>.
+[https://aws.amazon.com/premiumsupport/knowledge-center/create-and-activate-aws-account/](https://aws.amazon.com/premiumsupport/knowledge-center/create-and-activate-aws-account/).
 You should set the alias for this account to your project's name and
 the `org-root` suffix, like `spacecats-org-root`.
 
@@ -43,7 +43,7 @@ This needs to be done as the root user, so now is a good time.
 
 ## Bootstrap Terraform for org-root Account
 
-Following the pattern in <https://github.com/trussworks/terraform-layout-example>,
+Following the pattern in [https://github.com/trussworks/terraform-layout-example](https://github.com/trussworks/terraform-layout-example),
 set up your infra Git repo that we created earlier. Name the directory for this
 account after the account alias as usual. Then, `cd` into this directory and
 checkout the bootstrap repo like so:

docs/infrasec/bootstrap.md

@@ -68,7 +68,7 @@ project. This will allow you to store things like passwords and MFA codes
 for AWS accounts, GitHub "robot" users, and anything else that you need
 to give members of the team access to.
 
-You can create a new account by going to <https://1password.com> and
+You can create a new account by going to [https://1password.com](https://1password.com) and
 clicking on "sign in" in the upper right hand corner, and then instead
 of clicking on an existing account, click on "create a new account" at
 the bottom of the page, then click on "for my team" on the next page,
@@ -93,10 +93,10 @@ application to stand up yet, you should get this bootstrapped so that
 things are ready to go.
 
 If you are starting from scratch, you will need to open a new AWS account
-by going to <https://aws.amazon.com> and creating an AWS account, using
+by going to [https://aws.amazon.com](https://aws.amazon.com) and creating an AWS account, using
 the Truss admin card as the billing information. This account will be your
 `org-root` account that will start your
-[AWS Organization](./aws/aws-organizations.md). Once that is created, you
+[AWS Organization](aws-organizations.md). Once that is created, you
 should bootstrap Terraform in it and set up the `admin-global` namespace.
 Things you will want to set up in the `org-root` account:
 

docs/infrasec/certs.md

@@ -80,4 +80,4 @@ one-off certificates. Their documentation is
 
 ## External resources
 
-- How an SSL/TLS handshake works: <https://www.ssl.com/article/ssl-tls-handshake-overview/>
+- How an SSL/TLS handshake works: [https://www.ssl.com/article/ssl-tls-handshake-overview/](https://www.ssl.com/article/ssl-tls-handshake-overview/)