-
Notifications
You must be signed in to change notification settings - Fork 22
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.
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
ACA-1500: Create a common resource management convention for all roles #73
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nirarg
commented
May 20, 2024
p3ck
reviewed
May 20, 2024
tests/integration/targets/test_azure_load_balancer_with_public_ip/tasks/main.yml
Show resolved
Hide resolved
tests/integration/targets/test_azure_load_balancer_with_public_ip/tasks/main.yml
Show resolved
Hide resolved
anna-savina
reviewed
May 21, 2024
nirarg
force-pushed
the
resource-group-manage
branch
2 times, most recently
from
May 21, 2024 09:29
ad11dfe
to
5adad4a
Compare
nirarg
force-pushed
the
resource-group-manage
branch
2 times, most recently
from
May 22, 2024 10:15
061d843
to
e6fa214
Compare
anna-savina
reviewed
May 22, 2024
anna-savina
reviewed
May 22, 2024
anna-savina
reviewed
May 22, 2024
anna-savina
reviewed
May 22, 2024
anna-savina
reviewed
May 22, 2024
nirarg
force-pushed
the
resource-group-manage
branch
from
May 22, 2024 18:01
e6fa214
to
62c11ec
Compare
…ip" role This is done as part of Resource Group management convention changes for all roles Jira ticket: ACA-1500 The following rules must be followed: * The main file for each role should include the "Get Resource Group" task. * In the "Create" tasks: - Verify that if the resource group doesn't exist, the user must provide the region name. - If the resource group doesn't exist, create it with the given region name. * In the "Delete" tasks: - Verify that the resource group exists. - After all resources are deleted successfully, if the user requested to delete the resource group, delete it. - The role shouldn't include an option for force deleting non-empty resource groups. Also changing the integration tests to have 2 tests cases: 1. Pre created Resource Group 2. Resource Group has to be created and deleted by role
nirarg
force-pushed
the
resource-group-manage
branch
from
May 23, 2024 07:10
62c11ec
to
2352e91
Compare
anna-savina
reviewed
May 23, 2024
For more info check the description of the following commit: Change Resource Group management in "azure_load_balancer_with_public_ip" role
This change includes removing "azure_manage_postgresql_delete_option" variable and adding two specific boolean variables: - "azure_manage_postgresql_postgresql_delete_server" - "azure_manage_postgresql_postgresql_delete_resource_group" For more info check the description of the following commit: Change Resource Group management in azure_load_balancer_with_public_ip role
For more info check the description of the following commit: Change Resource Group management in "azure_load_balancer_with_public_ip" role
nirarg
force-pushed
the
resource-group-manage
branch
from
May 23, 2024 08:57
504dfa5
to
f561c9f
Compare
anna-savina
reviewed
May 23, 2024
nirarg
changed the title
[WIP] ACA-1500: Create a common resource management convention for all roles
ACA-1500: Create a common resource management convention for all roles
May 28, 2024
…c_ip" role This commit also fix an issue in which the "resource group role" including task was wrong For more info check the description of the following commit: Change Resource Group management in "azure_load_balancer_with_public_ip" role
For more info check the description of the following commit: Change Resource Group management in "azure_load_balancer_with_public_ip" role
nirarg
force-pushed
the
resource-group-manage
branch
from
May 28, 2024 13:08
f561c9f
to
4d7f4fd
Compare
LGTM |
1 similar comment
LGTM |
anna-savina
approved these changes
May 29, 2024
p3ck
approved these changes
May 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The following rules must be followed:
Also changing the integration tests to have 2 tests cases:
Roles changed in this PR:
azure_load_balancer_with_public_ip
azure_manage_networking_stack
azure_manage_postgresql
azure_manage_security_group
azure_virtual_machine_with_public_ip
The following roles are not changed in this PR:
azure_manage_resource_group
azure_manage_network_interface
- Its expected in the role that the Resource Group is already created with other dependency resources in it