Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create a separate container registry module for TF #24

Open
JouHouFin opened this issue Feb 25, 2021 · 1 comment
Open

Create a separate container registry module for TF #24

JouHouFin opened this issue Feb 25, 2021 · 1 comment
Assignees
@msrn
Labels
enhancement New feature or request ready-for-work

Comments

@JouHouFin
Copy link
Collaborator

JouHouFin commented Feb 25, 2021 •
edited
Loading

Currently the container registry is deployed within the K8S cluster resource group and consequently, destroyed every time the cluster is destroyed.

Write a TF module for deploying the container registry that has to be separately applied and destroyed. Also, see if lifecycle.prevent_destroy should be used in this case.

@msrn heads up!

linked to smaddis/common-issues#37
@JouHouFin JouHouFin changed the title Create a separate container registry resource group Create a separate container registry module for TF Feb 25, 2021
@JouHouFin JouHouFin added enhancement New feature or request ready-for-work labels Feb 25, 2021
@msrn
Copy link
Member

msrn commented Mar 1, 2021 •
edited
Loading

Work happening on my own fork at wip-static-cr branch msrn/smad-deploy-azure/wip-static-cr

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@msrn msrn

Labels
enhancement New feature or request ready-for-work
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@msrn @JouHouFin