function rather than variable to enable dynamic runtime calculation
e.g. for unit tests

move module-level variables into configure function, unneeded outside
module, wait for Django startup before using settings

similar to how this is done in the Terraform module

…t name

allow interfacing with Azure inside devcontainer

the secret does not contain any sensitive information
and is only configured in the dev environment

Because the SBMTD Mobility Pass enrollment pathway is available in production, I updates adoption status from "test" to "Live,"

Bumps [treosh/lighthouse-ci-action](https://github.com/treosh/lighthouse-ci-action) from 10.1.0 to 11.4.0.
- [Release notes](https://github.com/treosh/lighthouse-ci-action/releases)
- [Commits](treosh/lighthouse-ci-action@10.1.0...11.4.0)

---
updated-dependencies:
- dependency-name: treosh/lighthouse-ci-action
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>

…1873)

used to shortcut secret store for e.g. local testing

add some basic logging

Bumps [sentry-sdk](https://github.com/getsentry/sentry-python) from 1.40.0 to 1.40.2.
- [Release notes](https://github.com/getsentry/sentry-python/releases)
- [Changelog](https://github.com/getsentry/sentry-python/blob/master/CHANGELOG.md)
- [Commits](getsentry/sentry-python@1.40.0...1.40.2)

---
updated-dependencies:
- dependency-name: sentry-sdk
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

- Adds several new settings and Key Vault secrets
- Adds Django Google SSO package
- Fix: Django JS files are now allowed on Admin site
- Feat: Allow specific users with @complier.la emails to create and log into account on Admin

Azure KeyVault currently enforces the following rules:

    * The value must be between 1 and 127 characters long.
    * Secret names can only contain alphanumeric characters and dashes.

Read more about Azure KeyVault naming rules:
https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules#microsoftkeyvault

Read more about Django validators:
https://docs.djangoproject.com/en/5.0/ref/validators/#module-django.core.validators

* update definition to use new field
* update migrations
* remove env var from terraform definitions
* move default value to .env.sample

* update definition to use new field
* update migrations
* remove env vars from terraform definitions
* move default value to .env.sample

PemData favors the secret, but fallback to a remote URL
this is to allow for simpler turn-key local development

* update definition to use new field
* update migrations
* remove env vars from terraform definitions
* move default keys to .env.sample

Bumps [sentry-sdk](https://github.com/getsentry/sentry-python) from 1.40.2 to 1.40.3.
- [Release notes](https://github.com/getsentry/sentry-python/releases)
- [Changelog](https://github.com/getsentry/sentry-python/blob/master/CHANGELOG.md)
- [Commits](getsentry/sentry-python@1.40.2...1.40.3)

---
updated-dependencies:
- dependency-name: sentry-sdk
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

Co-authored-by: machiko <[email protected]>

Co-authored-by: machiko <[email protected]>

Co-authored-by: machiko <[email protected]>

…response formatting

Co-authored-by: machiko <[email protected]>

Co-authored-by: machiko <[email protected]>

Co-authored-by: machiko <[email protected]>

Co-authored-by: machiko <[email protected]>

Co-authored-by: machiko <[email protected]>

Co-authored-by: machiko <[email protected]>

Mermaid!

Removed "(Configurable Strings)" from all references to the copy spreadsheet. Since we moved away from configurable strings, the inclusion of this qualifier is no longer accurate and doesn't reflect the current name of the spreadsheet.

Replaces iframe displaying a Google doc.

This page currently links to a broken Figma file. I propose we remove it and bring it back when we have relevant content.

the vault is where backups are stored
the policy defines the frequency and retention of backups

these are linked to the storage account via azurerm_backup_container_storage_account

- increased linked text
- replaced CDT generic URL with a much more meaningful one

Bumps [django](https://github.com/django/django) from 5.0.1 to 5.0.2.
- [Commits](django/django@5.0.1...5.0.2)

---
updated-dependencies:
- dependency-name: django
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

Bumps [sentry-sdk](https://github.com/getsentry/sentry-python) from 1.40.3 to 1.40.4.
- [Release notes](https://github.com/getsentry/sentry-python/releases)
- [Changelog](https://github.com/getsentry/sentry-python/blob/master/CHANGELOG.md)
- [Commits](getsentry/sentry-python@1.40.3...1.40.4)

---
updated-dependencies:
- dependency-name: sentry-sdk
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

also remove workflow input to simplify since we don't use it

Docker, bash, etc. support multiline environment variables, by simply wrapping
the value in single quotes with newlines, e.g. in an .env file:

  multi_line_value='first line
  second line
  third line'

Resulting in the expected:

  $ echo "$multi_line_value"
  first line
  second line
  third line

Due to a quirk in VS Code's Python extension, multiline values are not parsed,
see https://code.visualstudio.com/docs/python/environments#_environment-variables

> ... Multiline values aren't supported ...

And more ongoing discussion at microsoft/vscode-python#18307

When running locally in e.g. Debug mode, and secrets are read dynamically from the environment, Python loses
the multiline value and we end up with:

  >> value = os.environ.get("multi_line_value")
  >> print(value)

  first line

This changes the samples and docs so literal newlines are added to the value of the environment variable in an .env file:

  multi_line_value='first line\nsecond line\nthird line'

But the initial value read by Python contains _escaped_ newline characters:

  first line\\nsecond line\\nthird line

Hence unescaping so that local secrets contain the actual newline character:

  first line\nsecond line\nthird line

)

remove duplicate django.contrib.messages.context_processors.messages

these have to be present in the .env file to reset the DB locally

reset_db.sh reuses the existing init.sh for other initialization

dumped the existing (prior to this deletion) data using Django manage.py,
excluding some model types that are defined and recreated by other migrations:

   python manage.py dumpdata \
    --exclude auth.permission \
    --exclude auth.user \
    --exclude contenttypes.contenttype > fixtures.json

then cleaned up the labels/names of our sample data for consistency

updates db_reset.sh to load these fixtures after migrations are run

updates the Cypress tests to use the new fixture location for sample data