search

buerokratt / POC-DMR.Cross-functional-requirements

Cross-functional requirements to take into account when developing or planning to develop Bürokratt's custom base components
MIT License
1 stars 1 forks source link

Feature/local terraform #48

Closed adelechurchill closed 2 years ago

adelechurchill commented 2 years ago

Addresses https://github.com/buerokratt/Infrastructure/issues/4 - Infrastructure: Setup terraform to provision infrastructure from dev machine

NB: the contents of the PR are an experimental (but fully functional) setup but will be copied over to the Infrastructure repo in another issue.

Addresses the following Acceptance Criteria

A Makefile is provided to make it easy to provision the necessary infrastructure for a basic AKS cluster and Key Vault, credentials can be entered using a tfvars file allowing local terraform execution

Below shows the created resource groups and associated resources: Resource Groups - one is created by default by aks rgs_created_from_local_tf General Resource Group Resources rg_resources AKS Cluster Resource Group Resources managed_cluster_resources

martinkearn commented 2 years ago

@Adele-Churchill-13, I've worked out that this PR is for https://github.com/buerokratt/Infrastructure/issues/4 from the previous sprint.

It cannot be tagged because the PR and issue are in different repos, which seems odd. What was the reason for that?

If the PR is correctly in the "cross" repo, can we move the issue so that it can be tagged to the PR?

adelechurchill commented 2 years ago

@Adele-Churchill-13, I've worked out that this PR is for buerokratt/Infrastructure#4 from the previous sprint.

It cannot be tagged because the PR and issue are in different repos, which seems odd. What was the reason for that?

If the PR is correctly in the "cross" repo, can we move the issue so that it can be tagged to the PR?

This task followed on from the Base Terraform which has initially been added to the Cross Functional Requirements repository, at the time of development the intended place for this feature was being restructured, due to sprint end and MS1 approaching the decision was made to progress with the task in the current repository - with plans to migrate to the Infrastructure repository

decodingahmed commented 2 years ago

@Adele-Churchill-13, I've worked out that this PR is for buerokratt/Infrastructure#4 from the previous sprint. It cannot be tagged because the PR and issue are in different repos, which seems odd. What was the reason for that? If the PR is correctly in the "cross" repo, can we move the issue so that it can be tagged to the PR?

This task followed on from the Base Terraform which has initially been added to the Cross Functional Requirements repository, at the time of development the intended place for this feature was being restructured, due to sprint end and MS1 approaching the decision was made to progress with the task in the current repository - with plans to migrate to the Infrastructure repository

Just adding to what @Adele-Churchill-13 said, here is the ticket to move this work into the infrastructure repo: https://github.com/buerokratt/Infrastructure/issues/12

She also mentioned in the PR description that the intention is to move a lot of this over.