In this video I show you how to add CORS support to an Azure Application Gateway Route
Today while adding a new server to an Azure subscription I encountered the following error:
The subscription is not registered to use namespace 'Microsoft.HybridCompute'
In this video I show you how register the Hybrid Compute provider in your subscription to overcome this obstacle.
In this video I show you how to use AWS API Gateway to quickly proxy an existing API.
So you’ve started using terraform
You’ve progressed to creating terraform modules
You’ve put your module in a private bitbucket repo
Now you want to access it from a bitbucket build pipeline and you see the following
In my case I reached out to one of my friendly devops colleagues @BlnaryMlke who showed me how ssh keys and git hang together, I don’t know if i should be ashamed to say I’ve never used git with ssh keys until today.
Armed with this new knowledge I set off to do the same in my bitbucket pipeline only to discover that Bitbucket has some primary support for this scenario!
What follows are the steps required in a bitbucket pipeline in order to to use a private git bitbucket repo that contains a terraform module
1) First create a new key in the the project that contains your pipeline (i.e. the project that is including the terraform module), you’ll find this option under project settings, pipelines/ssh keys
Image shows that I’ve added a new Key and then added bitbucket.org (fetch gets the fingerprint)
2) Now add the public key to your bitbucket git repo that contains the terraform module, to do this you go to the project settings and choose access keys then add
3) Lastly, you’ll need to configure your terraform module source with the following format
That’s it, huge thanks again to @BlnaryMlke for setting me on the right path
4) Bonus Step: If you wish to work outside the bitbucket pipeline and don’t want to use ssh keys but rather your OAuth token you can configure git insteadof to automagically redirect ssh to http
In this video I show you how to configure multiple origins for a single cloudfront distribution
In this video I show you how move application secrets into Azure Key Vault without any code changes.I do this by using a vault access policy.
Note: You'll have to ignore my managed identity references in this video I didn't use them.
In this video I show you how to leverage Azure Managed Identities to allow access between Azure resources.
(excuse the audio quality.. i need to improve on this)
I believe I’ve previously covered c# generics covariance and contravariance in the past, now it’s javas turn
As you may or may not know
The term PECS stands for “Producer Extends, Consumer Super,” which is an odd acronym coined by Joshua Block in his Effective Java book, but provides a mnemonic on what to do. It means that if a parameterized type represents a producer, use extends. If it represents a consumer, use super. If the parameter is both, don’t use wildcards at all—the only type that satisfies both requirements is the explicit type itself.
Covariance in java uses the extends keyword (yes even with interfaces), e.g. List<? extends Number> accommodates all types that derive from Number
Contravariance on the other hand uses the super keyword e.g. List<? super Number> accommodates all the types that Number derives from and of course number itself.
So what exactly is PECS recommending we do?
- Use extends when you only get values out of a data structure
- Use super when you only put values into a data structure
- Use the exact type when you plan on doing both
If you are debugging with VS2017/9 and want to pass environment variables to your container then read this post, if you are looking for picture of cats then sorry but leave a comment how you got here
Create a new text file, the name doesn’t matter, but i called mine Dockerfile.env
Add this file to your .csproj file.
Not really a step but you you can simply query your Environment variable in the usual fashion (Environment.GetEnvironmentVariable())
Needless to say when you run in production you’ll need to pass the Environment variable according to Docker documentation which I don’t cover here