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.

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

[QUESTION]:Arm Template / az-cli support for Playwright Workspace #69

Open
ranat5 opened this issue Nov 3, 2023 · 4 comments
Open

[QUESTION]:Arm Template / az-cli support for Playwright Workspace #69

ranat5 opened this issue Nov 3, 2023 · 4 comments
Assignees
Labels
enhancement New feature or request

Comments

@ranat5
Copy link

ranat5 commented Nov 3, 2023

Hi Team,
As per the Playwright (preview) documentation for setting up the workspace in Azure, these seem to be done in manual steps. Is there currently any support for setting this up via az-cli or a more preferred option via arm templates (Bicep)?

Thanks!

AB#1912813

@johnsta
Copy link
Contributor

johnsta commented Nov 7, 2023

Hi @ranat5, as of now, we do not have support for automating workspace creation using Azure CLI or ARM templates. But I can confirm that it is on our roadmap as part of our commitment that ensures all Azure services have this functionality.

@johnsta johnsta added the enhancement New feature or request label Nov 7, 2023
@ranat5
Copy link
Author

ranat5 commented Nov 7, 2023

Hi @johnsta, Does not need to be precise, but any sort of timeline we can get, as to when this can be expected? :)

@mburumaxwell
Copy link

Bicep worked for me today:

resource playwright 'Microsoft.AzurePlaywrightService/accounts@2024-02-01-preview' = {
  name: 'somename'
  location: location
  properties: {
    regionalAffinity: 'Disabled'
    reporting: 'Enabled'
    scalableExecution: 'Enabled'
  }
}

@KuberDriver
Copy link

Bicep worked for me today:

resource playwright 'Microsoft.AzurePlaywrightService/accounts@2024-02-01-preview' = {
  name: 'somename'
  location: location
  properties: {
    regionalAffinity: 'Disabled'
    reporting: 'Enabled'
    scalableExecution: 'Enabled'
  }
}

Does this work without errors on incremental deployment? i.e. when you redeploy does it proceed without any errors for you?
currently I am seeing following error:

The operation for resource '/subscriptions/****************/resourceGroups/rg-sandbox/providers/Microsoft.AzurePlaywrightService/accounts/fdcsb' is invalid as it is being provisioned with state: 'Accepted'. (Code: InvalidResourceOperation)

Hi @johnsta checking if there is any progress on official support for PW IaC deployment with ARM/Bicep?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants