* WIP: doesn't work yet
* Make temporary changes to the makefile
* Fixes to firewall submodule
* Update Makefile
* move firewall name to locals
* Init porter bundles for Gitea and Nexus
* Add parameters to the new porter bundles
* Revert "Convert data inputs into variable inputs for modules in Terraform (#1154)"
This reverts commit c3e2cb7f0a.
* WIP: moving variables around for Gitea
* Update Gitea module to consume variables from data
* Fix several problems in firewall module
* Changes to Gitea terraform (fix state container, add az login for local-exec)
* Initial Nexus porter configuration
* Add Sonatype-Nexus bundle
* Uncomment firewall lock, fix local-exec command
* Fix comments
* fmt
* Gitea, Nexus: Move variable inputs to data and locals
* change path to nexus.properties
* temporarily remove arm_client_id
* fmt
* remove unused arguments
* fmt
* Use key_vault_reference_identity_id in Terraform
* Remove unused variables
* Deploy Firewall, Gitea and Nexus as part of the main build
* Add deploying of shared services to tre-deploy command
* Add uninstall back
* WIP: working transfer of state for Firewall
* WIP: fiddling with more states
* WIP: fix removal of terraform state
* Add import script for Gitea
* fixup tre-start/stop make target naming
* strip '-' from string in storage account name
* removed state_remove for gitea + nexus
* removed state_remove for gitea + nexus
* local modifications of import/remove state scripts
* fw / gitea / nexus deploy from local via tf functional
* gitignore
* bumped gitea version
* tf linting
* PR updates
* vars for ci
* added check_dependencies to login in CI
* check for non-existing RG and skipping import state if we're in a fresh CI
* removed lock from remove/import scripts
* remove/import state for gitea
* gitea and nexus state moved
* nexus + gitea state moved, apart from storage share
* fixed storage import
* PR snags
* override
* kv uri
* new secret import style
* secret
* secret
* state list
* state list
* remove state fix
* remove state special chars
* importing random_password to prevent KV updating
* moved make target out of default path
* supress risky log output
* unwound gitea/nexus state moving debacle
Co-authored-by: Tanya Borisova <tborisova@microsoft.com>
Co-authored-by: Ross Smith <ross-p-smith@users.noreply.github.com>
Co-authored-by: Stuart Leeks <stuartle@microsoft.com>
* Add unit tests into tasks
* Move Unit Tests back into Docker build
* workflow dispatch condition
* Catch the exit code
* Always output the test results
* Putting Unit Tests back to previous behaviour
* missed debug
* Allow pytest to fail, but build carries on
* Force failure
* Discover directory
* Check file existence
* Remove failing test
* Make Java fail
* Remove the failed java test
* typo
* Does the workflow fail on the publish step only
* Some linting
* Linting problems!
* Missing URI
* More missing URI
* Output terraform plan into a different file each time (named with the same prefix as a log file)
* Add a script to compare terraform output files
* simplify the script
This PR just contains a few changes to the Dev Container configuration that I found helpful working with it.
* The container now mounts the ~/.azure directory, so that it uses the same Azure CLI profile that is configured on the host. (means you don't have to keep doing an `az login --use-device-code`.
* The container mounts the bash history file from the host, so command history is preserved and specific to the project.
* The Dev container now runs as the __vscode__ user, not __root__.
- When using WSL this mean that new files are not created as root, so you still have access when outside the container.
- It's also good practice not to develop as root.
* The `pip install requirements.txt` is moved to the end of the Docker file so that changes to __requirements.txt__ doesn't cause all the `apt install`s to run again.
* The running container is named `tre`. This is a bit of a personal preference and does have a trade-off.
- The benefit is it make it easy to set up a profile in Window Terminal to run `docker exec -it tre bash` so you can have dev container shell outside VS Code.
- The slight downside is the fixed name means you can only have one instance of the dev container running.
Add scripts to bootstrap TF environment, build and push docker images, and deploy the TRE.
- Add TF bootstrap scripts and templates to create TF state storage and ACR
- Add scripts to build and push the docker images
- Add deployment scripts to core TF templates
- Remove GitHub packages integration
- Set linter to run locally as we have already checkout out the files
Ross Smith
Tamir Kamara
Martin Peck
Stuart Leeks
David Moore
Elad Iwanir
tanya-borisova
Tess Ferrandez
Denis Cepun
Marcus Robinson
Stephen Askew
Tomi Paananen
Limor Lahiani
Tess Ferrandez