I would assign this step to a team which as only project viewer right and it's not possible. What are the role permission to have ? Added to the responsibility team
I prefer a quad configuration with tentacles placed at 90 degree spacing on the horizontal plane. This gives the quadapus the most stability. A 2x2 or side by side configuration is very impressive but unstable.
it would be great if instead of introducing new concepts you first could give idea how this benefits devops or dev team with some common existing set of tools and clouds (e.g. GitlabCI + Terrafor IaaC/AWS + K8s +ArgoCD + web-app code with several tiers)
Thanks for your comment! There are so many tools out there, right? 😀 Covering all of them is a challenge! For what it's worth, we have several videos featuring the technologies you've highlighted. And we'll continue to produce videos on integration scenarios like the ones you've highlighted. All we ask is that you subscribe to get notified when a new video is published. 👍
Oh man, I was just googling this when I thought to check to see if someone posted the link in the comments. Thats a bummer that they didn't find the link.
Terraform is (indeed) great. Bicep (however) does provide some nice features for Azure over the HCL/provider model espoused by Terraform. :) But, you can do well with either solution.
One thing I didn't take in is the evidence that the change took place. It wasn't shown the before and after of that config file being changed. How does one go about just making a change to an already created file? I know the name and location of the file, I know what needs to be changed, I just don't see how I can tell this magical software HOW to change what I need changed.
Great episode, I would love to get into depth with Kubernetes , but to properly get a handle It would be a big challenge. I find there isn't enough people interested to becoming a Full time Kubernetes devops expert.
Hey Thomas, I still have a copy of your Windows PowerShell 2.0 Bible book that I won from a Q&A on Spiceworks about ten years ago! I loved the conv. thanks for sharing your wisdom with us.
The main excitement behind the Frozen collections over ReadOnly was this sentence: >>> These types provide an immutable surface area such that, once created, no changes are permitted to the keys or values. <<< To which I then asked, why not use the available Immutable collection types? The best explanation I've seen of this out on the interwebs: >>> ImmutableSet and ImmutableDictionary are designed to be immutable and to make it easy to create slightly modified copies of a given instance at a reasonable cost. So imagine you create an immutable set with a million entries in it. You cannot mutate this set since it is immutable. Now, you need a new set with 1 extra entry. You could recreate the set from the ground up, which would be very expensive. Instead, you can start from your original immutable set and apply a delta to create a new distinct set instance which under the covers shares most of the state from the original set. You use less memory this way, and it takes much less time to create the new instance. The problem is that in order to allow this mode of operation, ImmutableDictionary and ImmutableSet are complex implementations which introduce substantial compromises in overall read performance as a trade-off for this ability to make cheap delta clones. FrozenSet and FrozenDictionary do not provide the delta clone ability, they are optimized strictly for fast read performance. You pay more for creation, you pay more for making a clone with modifications, as a trade-off for getting faster steady state read performance. <<< HTH
Obviously this video was made quite a while ago, but I wanted to ask - if you had "MyProject" and "MyProjectAlso" - would the 'name=MyProject' search show both of them? If so, is it possible to narrow your search to only find exact name matches or would you just have to parse through the results and do name matching in the calling program/script/whatever?
git have recently changed their authentication process, when following the above i'm faced with an authentication issue. I have added my authentication token as a credentials parameter however still face the same issue. is there a fix for this?
Maybe I missed it, but Is there a way of having the system enforce that a particular branch always be used to deploy to certain environments? I assume you can use your custom branch (fix-up-english) to test out the changes in the dev environment. But your security team would probably also want to lock down the branch used for QA, Staging, and Production to always use the deployment code that has been reviewed in main.
At the time of this writing no, that is not possible. We are seeing some work being shaped around branch protection policies, so something might come from that. Once something like that is added, we will be sure to announce it.
@@OctopusDeploy Is there an update on this? It looks like using git ref and git commit will let you do that but I cant get it to use anything other than master from Azure DevOps.
