Padawan updated site deployment paths
January 1, 2023
In an effort to increase security, we are making a slight change to the path where sites are deployed in the multi-tenant NGINX instances. Sites will now be deployed to /sites/[site-slug] instead of /sites/[site-name]. The site-slug is the full path of your source code repo, rather than just your repo name.
When did this go into effect?
Monday, January 9th, 2023
What does this mean to me?
Very little - this announcement is more of an FYI. The only visible difference will be if you use the default https://websites[.staging].dso.mil url to access your site. In that case your site will have a new url (repo name replaced by site slug). See one of the Padawan index pages to find the new URL of your site which will use the site slug:
- IL2 Staging: https://websites.staging.dso.mil/
- IL2 Production: https://websites.dso.mil/
- IL4 Staging: https://websites-il4.staging.dso.mil/
- IL4 Production: https://websites.il4.dso.mil/
Example please?
Let's take npm-hello-world as an example. The source code repo is https://code.il2.dso.mil/platform-one/products/bullhorn/padawan/examples/npm-hello-world - which means that the site-name is npm-hello-world (the repo name) and it is currently deployed to https://websites.staging.dso.mil/sites/npm-hello-world/
Now, the site will be deployed to https://websites.staging.dso.mil/sites/platform-one-products-bullhorn-padawan-examples-npm-hello-world/
What code changes do I have to make?
No changes are necessary in your repo! Your site will now be deployed to the site-slug moving forward.
What if I have a custom DNS entry?
No action is needed! The Padawan team will set your Istio VirtualService to point to the new site slug path.
What if I have a custom Content-Security-Policy or other custom NGINX config?
No action is needed! The Padawan team will update the custom NGINX location blocks across IL2 and IL4 staging/prod to point to the new site slug path.