mitzen

While seems confusing, i think it is pretty clear it meant what it says. If you have any changes, please commit or stash it - make sure your branch is clean and neat :) Or sometimes if you don't have any modification, just run the command "git reset". And re-run the command.

Here is the inline scripts that allow you to connect / authenticate using powershell extension in azure devops.

Not really sure why, az cosmodb keys don't work although it is available in the documentations. So instead i tried cosmosdb list-keys And that works. Feature or bug?

In Azure devops, there is an extension called PowerShell for Mac, Windows and Linux. This is not the same as "Azure Powershell" which is targeted to run on window build host / agent. Most of the time, I prefer to work with scripts based instead of inline scripts for tracking reasons. Az cli extension will automatically login for you and you can start running various scripts. This extension, requires a manual login approach. To installed a module, just do something like this Install-Module -Name CosmosDB -Force Some faq here Can I used az cli based command here? Yes you can. Can be as simple as follow :- az login --service-principal --username $env:CLIENTID --password $env:CLIENTSECRET --tenant $env:TENANT_ID az account set --subscription $env:SUBSCRIPTION Or using powershell (you need to use "ConvertTo-SecureString". Pretty sure the following Write-Host ( "init credential" ) $passwd = ConvertTo-SecureStri...

for some reason i am getting, specials unicode ( https://en.wikipedia.org/wiki/Specials_(Unicode_block)  and just mess up my stored procedure deployment to cosmo "cosmodb from the powershell gallery module". All it needs is a editor "Notepad++ and click on the options "Show all characters" and edit away! :)

First you can create a folder to place all these files and make sure you have powershell installed Create your powershell module with a psm1 extension You can copy and paste the cod from here , just make sure you have the right eten Setup your module manifest New-ModuleManifest -path ./firstmodule.psd1                                                                                                                      Edit firstmodule.psd1 and add the following Description = 'demo module This basically gives it the minimum requirements :) Publish-Module -path /Users/jeremy/tmp/work/powershell/firstmodule -nugetapikey    

When you sign up for a community edition, you tend to create notebook with it. If you want to make use of the existing database, you can load it using the following command : To load a table called airlineflight use databricks; select month from airlineflight where year == 2002 To convert to a data frame you can use the following command :- %python  df = sqlContext.sql("Select * from airlineflight") And from this point onwards, you can manipulate using filter, select. Please refer to documentation here . Some quick examples, %pytho df.select("FlightNum").collect() df.filter(df.DepTime>24).count()

Documentation for Databricks Cloud / Community. Finally manage to zoom in on what spark library that i am working on to progress further. Having my notebook in Python allows me to work and then subsequently use function defined here. http://spark.apache.org/docs/latest/api/python/pyspark.sql.html#pyspark.sql.functions.concat

I guess the concept is pretty easy but just that we just lost in piles of documentation. Key concepts is when you build make sure you publish your output as an artefact.  How do you do that? Depends on  whether you're building a  .netcore or javascript based project. If you're using dotnet core, you just use "publish and zip" artifact. If you're using javascripts, then you need to publish your artifact to  drop folder.  For eample,  we have PublishBuildArtifact here generate dll into a drop folder steps : - script : dotnet build src/AzureFunctionApp.sln --configuration $(buildConfiguration) displayName : 'dotnet build $(buildConfiguration)' - script : dotnet publish src/AzureFunctionApp.sln --configuration $(buildConfiguration) displayName : 'dotnet publish src/AzureFunctionApp.sln $(buildConfiguration)' - task : PublishBuildArtifacts@1 inputs : PathtoPublish : '$(Build.ArtifactStagingDirectory)' ...

When you try to copy files to $web in your static site (Azure storage account), you need to escape $web otherwise you won't be able to copy files across. So typically you do something like az cli storage upload-batch -s sourcefolder -d destinationfolder  \$web Especially when you on a Mac or Linux based system.

Install nuget dotnet add package Microsoft.ApplicationInsights.AspNetCore --version 2.7.0 Setup codes, startup.cs public void ConfigureServices ( IServiceCollection services ) { // The following line enables Application Insights telemetry collection. services.AddApplicationInsightsTelemetry(); // code adding other services for your application services.AddMvc(); } application.json "ApplicationInsights" : { "InstrumentationKey" : "putinstrumentationkeyhere" }, In the section, "putInstrumentationkeyhere" --- place the guid created for app insights in your portal.

Setup kafka bin /zookeeper-server-start .sh config /zookeeper .properties bin /kafka-server-start .sh config /server .properties Create a topic bin/kafka-topics.sh --create --zookeeper localhost:2181 --replication-factor 1 --partitions 1 --topic test To write something to your topic bin/kafka-console-producer.sh --broker-list localhost:9092 --topic test Working with spark You can get the script from here . To submit spark python code spark-submit --packages org.apache.spark:spark-sql-kafka-0-10_2.11:2.4.1 kafka.py localhost subscribe test

In this example, we are running a spark python file called test.py.  spark-submit test.py /home/jeremy/test/test.dat

pyspark --packages com.microsoft.azure:azure-eventhubs-spark_2.11:2.3.10

Static cloud based resource provisioning is bad. Tools such as terraform needs a dynamic scripting language. There are so many resources created with any kinda of FQDN. And there is not alot of choices to choose from and conflict often occurs. We need a better cloud provision tool that resolve conflict better or provides a scripting interface.

You can easily configure Azure function to pull secret value from KeyVault. First you need to setup :- 1. Azure function function -> Platform feature -> Identity -> Go ahead and turn on the identity. This is what the called Managed Identity setup as you will get an App Id (guid). Save it and then setup your vault below :- 2. In your Key Vault, Access policy -> Add New -> Select Principal -> Add the name of your Azure function app Id 3. Restart your azure function app. 4. In your settings file, you can have some an configuration entry say, CONN_WEB_APP with the following value, @Microsoft.KeyVault(SecretUri=https://blahblahblah.vault.azure.net/secrets/Conn/e74dfd34e8e4415fbd09c540de2cf556) You're all sorted! :)

If you encounter this issue, you are probably using older version of azure function tool. To upgrade, use the following command :- sudo npm i -g azure-functions-core-tools@core --unsafe-perm true Then try to publish your app again :- func azure functionapp publish ClaimSubmissionFunction

To add new solution dotnet new sln To add existing project into the solution dotnet sln AzureFunctionApp.sln add ClaimSubmission/ClaimSubmission.csproj

Added reducer or store pretty much the same thing, to me. To setup the required libraries, npm install @ngrx/store --save First you need some sort of actions import { Action } from '@ngrx/store' ; export enum ActionTypes { Login = 'Login' , Logout = 'Logout' , Reset = 'Reset' , } export class Login implements Action { readonly type = ActionTypes . Login ; } export class Logout implements Action { readonly type = ActionTypes . Logout ; } export class Reset implements Action { readonly type = ActionTypes . Reset ; } export type ActionsUnion = Login | Logout | Reset ; Then you setup your reducer :- import { ActionReducer , ActionReducerMap , createFeatureSelector , createSelector , MetaReducer } from '@ngrx/store' ; import { environment } from '../../environments/environment' ; import { ActionsUnion , ActionTypes , Login } from ...

To install effects, use the following cli :- npm install @ngrx/effects --save To add effect, you need to setup your Store reducer first. After that everything is so much easier. You only requires this piece of code to setup your effects :- import { Injectable } from '@angular/core' ; import { Actions , Effect , ofType } from '@ngrx/effects' ; import { ActionTypes } from './actions/Login' ; import { map , mergeMap } from 'rxjs/operators' ; @ Injectable () export class AppEffects { constructor ( private actions$ : Actions ) { } @ Effect () loginEffects$ = this . actions$ . pipe ( ofType ( ActionTypes . Login ), map ( action => { console . log ( "login effect taking place...." ) return ({ type: "tested" }); })); } And then configure it, in the app.module.ts imports: [ BrowserModule , FormsModule , AppRoutingModule , StoreModule . forRoot ({ login :...