Is it possible to rename or edit a User in Databricks (in Azure) once they have been created?
When I was first given access to Databricks, the admin spelled my last name incorrectly. From that point on, every time I create something it pulls in that incorrect last name. This even happens after changing Azure subscriptions and creating a brand new workspace myself and therefore the Admin. However, I cannot find any option to edit a user, including my own user info.
For example, when I go to create a new cluster, it pulls in the misspelled last name:
Related
I'm trying to add a VM start/stop solution on a second Automation second because i was not able to edit the solution on the first automation account to change the timings. Anyways, i've deleted all resources pertaining to the first Start/stop VM solution i had on the first automation account. After that i created a second automation account and tried to deploy the start/stop solution but i'm getting the following error,
"The resource 'ScheduledStartStop_Parent' already exists in location 'eastus' in resource group 'VM'. A resource with the same name cannot be created in location 'australiacentral'. Please select a new resource name."
Is there a waiting period only after which the resource actually gets deleted from the resource group? because i've already deleted this reource and its still giving me an error stating its still there. Can someone please explain why this is so? thanks a lot
When you have deleted the start stop solution, it doesn't delete all the resources related to it which are present in resource group. To delete them, traverse to the resource group, select the hidden items check box and delete the hidden resources. For your reference, providing a snapshot of hidden resources.
I'm pursuing DSC as a lightweight solution for managing local user accounts on distributed Windows instances in favour of connecting said instances to Active Directory.
Adding and removing specified local users works as expected, but I also want to check that ONLY the specified accounts exist (or are enabled) on each configured node.
e.g. - If I were to create a new local admin account with 'xUser CreateUserAccount / Ensure = Present', if I were to remove the code from my DSC script, that user would still exist on the target node. Similarly, if someone were to create a local user account by some other means, there would be no warning of the unexpected configuration drift through the DSC server.
To remove any unexpected accounts, I would first need be made aware of these accounts by some other means, and then specify 'xUser RemoveUserAccount'.
I have not found a way around this with the first 100 Google results on the topic. Has anyone solved this apparent conundrum with DSC? Should I rather look to something else e.g. Terraform?
I'm new to Azure platform. I'm trying free trial and creating a CI/CD setup for docker by following from the below link.
https://www.azuredevopslabs.com/labs/vstsextend/docker/
I have no issue until setting up build definition. I'm getting below issues when doing changes in the release definition.
when i click on "Authorize" button in azure subscription, I'm getting below issue.
Please let me know what mistake i am doing.
well, the text says it all. you are trying to create a connection with a name that already exists. you need to call it something different or rename the existing one
I have created a new service connection and mapped in the release definition.
Click on Manage link
Click on New service connection button
at top right corner
Select Azure resource manager
Once you select the respective option and click Next. Enter valid name and select respective subscription and resource group details.
I created a couple of Azure API connections and it allows me to change the display name, but there is no way to change the name itself. Apparently, it automatically creates the connections based on the connection type. Is there a way to control this?
Yes, you could deploy API connector and change its name with Template. If you already have a API connector, click it then choose Automation script and click Deploy.Like the below pic shows.
Now choose Edit template and for convenience delete the parameters and resources you don't want to use. In here you could change defaultValue as the name ,after modify the template would be like the pic shows, then click save. I fthe name in SETTING is not changed you also could change it here.
And the result shows the API name is not the original default name.
Note: This way is only used to deploy the API connectors.
Hope this could help you, if you still have other questions, please let me know.
When I try to create a new Azure Redis Cache and choose a location I just get a "There are no locations available." message.1 Setting everything else first still results in the same error. Refreshing the page doesn't resolve the issue. The problem occurs in both IE and Chrome.
Thanks for reporting this. It seems to be a bug in the portal. I can reproduce it if I click "Location" immediately after the "New Redis Cache" blade opens. However, if I wait a few seconds before clicking "Location", it doesn't repro.
As a workaround, if you close and reopen the "Location" blade it should populate correctly.
We will also work on fixing this in the portal.
Finally, for any issues with Azure Redis Cache you can contact us via email at azurecache#microsoft.com.
After working with the Azure team via email we were able to narrow down the problem and find a workaround.
There are 3 problems at work here that result in my symptoms:
The various New blades in the portal will default you to a disabled subscription. I believe they currently default to the first subscription (oldest) which may not be an active subscription. This results in the default behavior upon choosing a blade to be that of no-subscription.
The New Redis Cache blade will only show locations if you have selected a valid (not disabled) subscription. This behavior differs from the other New blades (such as Create VM) which will show you locations even if you have a disabled subscription selected.
Changing the resource group will automatically change the subscription and lock it, but changing the subscription in this way will not trigger an update to the blade. This means that the locations don't get updated for the new subscription because the subscription-changed-event (made up name) was not fired. In my case, I was always changing the subscription by way of changing the resource group, so I was never able to set the location.
The workaround:
Simply change to an active subscription before choosing a resource group. This will cause the locations list to be updated, and you can then choose a resource group after.