Skip to content
New issue

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

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

Already on GitHub? # to your account

Align locks accross all modules #197

Merged
merged 8 commits into from
Oct 19, 2021
Merged

Align locks accross all modules #197

merged 8 commits into from
Oct 19, 2021

Conversation

AlexanderSehr
Copy link
Contributor

Change

  • Align locks accross all modules
  • Leverages approach implemented by @MariusStorhaug to allow the user to choose which level of lock to apply

Type of Change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update (Wiki)

Checklist

  • I'm sure there are no other open Pull Requests for the same update/change
  • My corresponding pipelines / checks run clean and green without any errors or warnings
  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation (readme)
  • I did format my code

@MariusStorhaug MariusStorhaug self-requested a review October 19, 2021 07:03
@AlexanderSehr AlexanderSehr merged commit 43831de into main Oct 19, 2021
@AlexanderSehr AlexanderSehr deleted the users/alsehr/locks branch October 19, 2021 07:53
resource serviceBusNamespaceQueue_lock 'Microsoft.Authorization/locks@2016-09-01' = if (lockForDeletion) {
name: '${split(serviceBusNamespaceQueue.name, '/')[1]}-doNotDelete'
resource serviceBusNamespaceQueue_lock 'Microsoft.Authorization/locks@2016-09-01' = if (lock != 'NotSpecified') {
name: '${serviceBusNamespaceQueue.name}-${lock}-lock'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure about the naming here. If the queue namespace would refer to full name or resource specific name

- '${split(serviceBusNamespaceQueue.name, '/')[1]}-doNotDelete'
+ '${serviceBusNamespaceQueue.name}-${lock}-lock'

resource managedInstanceDatabase_lock 'Microsoft.Authorization/locks@2016-09-01' = if (lockForDeletion) {
name: '${split(managedInstanceDatabase.name, '/')[1]}-doNotDelete'
resource managedInstanceDatabase_lock 'Microsoft.Authorization/locks@2016-09-01' = if (lock != 'NotSpecified') {
name: '${managedInstanceDatabase.name}-${lock}-lock'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure about the naming here. If the managedInstanceDatabase would refer to full name or resource specific name

- '${split(managedInstanceDatabase.name, '/')[1]}-doNotDelete'
+ '${managedInstanceDatabase.name}-${lock}-lock'

@MariusStorhaug
Copy link
Contributor

Binary?

  • arm/Microsoft.AnalysisServices/servers/readme.md
  • arm/Microsoft.ApiManagement/service/readme.md
  • arm/Microsoft.Network/applicationGateways/readme.md
  • arm/Microsoft.Network/privateEndpoints/readme.md
  • arm/Microsoft.Network/publicIPAddresses/readme.md

Updated files, missing counterpart:

  • arm/Microsoft.Compute/virtualMachines/readme.md - missing bicep update?
  • arm/Microsoft.ContainerRegistry/registries/readme.md - missing bicep update?
  • arm/Microsoft.DataFactory/factories/readme.md - missing bicep update?
  • arm/Microsoft.EventHub/namespacesResources/eventhubs/readme.md - missing bicep update?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants