Versioning смотреть последние обновления за сегодня на .

Software Versioning Explained - Semantic (SemVer), Calendar (CalVer), etc.


How do we version software? Should we use build numbers, Semantic Versioning (SemVer), Calendar Versions (CalVer), milestone versioning, or something else? What are the reasons for using each of those and which one should you use? #versioning #semver #calver #semanticversioning #calendarversioning Consider joining the channel: 🤍 ▬▬▬▬▬▬ 🚀 Courses, books, and podcasts 🚀 ▬▬▬▬▬▬ 📚 DevOps Catalog, Patterns, And Blueprints: 🤍 📚 Books and courses: 🤍 🎤 Podcast: 🤍 💬 Live streams: 🤍 ▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬ ➡ Twitter: 🤍 ➡ LinkedIn: 🤍 ▬▬▬▬▬▬ Timecodes ⏱ ▬▬▬▬▬▬ 00:00 Intro 00:44 Types of versioning 01:08 Build number versioning 02:55 Calendar versioning (CalVer) 06:11 Semantic versioning (SemVer) 13:01 Milestone versioning 14:24 Random versioning 15:03 Geeky versioning 15:46 Which versioning should you use?

Dealing with and managing versioning


In this episode of Cloud Storage Bytes, Jenny Brown goes over how to use Cloud Storage object versioning, enabling versioning, disabling versioning, and much more! Guide - Object Versioning → 🤍 Guide - Viewing the object metadata → 🤍 Guide - Listing archived object versions → 🤍 Cloud Storage Bytes → 🤍 Subscribe to GCP → 🤍 Product: Cloud Storage; fullname: Jenny Brown; #CloudStorageBytes

What is Semantic Versioning?


What is the purpose of the semantic versioning? Each NPM package must have package version that is based on the semantic versioning. Each version consists of the major, minor and patch versions. There is also an option to add -beta or -alpha suffixes that indicate pre-release versions of the software. If you publish public NPM package you must increment package version each time when package is updated. 🔥 Wanna learn more? All software development courses that I teach 🤍 🎦 YouTube 🤍 🙍 LinkedIn 🤍 📪 Twitter 🤍 🔥 Discord community 🤍 🔥 Udemy Profile 🤍 SUBSCRIBE IN SOCIAL NETWORKS 🎦 YouTube 🤍 🙍 LinkedIn 🤍 📪 Twitter 🤍 Email 📧 in case you want to send me a notice bstashchuk🤍

REST API - Versioning REST APIs


REST API - Versioning REST APIs watch more videos at 🤍 Lecture By: Mr. Ravikiran S, Tutorials Point India Private Limited

What Is Semantic Versioning?


Semantic Versioning Blog Article: 🤍 🌎 Find Me Here: My Blog: 🤍 My Courses: 🤍 Patreon: 🤍 Twitter: 🤍 Discord: 🤍 GitHub: 🤍 CodePen: 🤍 #Shorts

Elegant API Versioning in ASP.NET Core (Web API)


Become a Patreon and get source code access: 🤍 Check out my courses: 🤍 Hello everybody I'm Nick and in this video I will show you how you can use Microsoft's versioning package to add versioning for your ASP.NET Core APIs. I will cover almost every feature of the package so by the end of the video you should be able to create a versioning strategy exactly as you like it. Don't forget to comment, like and subscribe :) Social Media: Follow me on GitHub: 🤍 Follow me on Twitter: 🤍 Connect on LinkedIn: 🤍 #dotnet #api #versioning

What is Software Versioning?


MultiSoft Corporation - International MLM Software Western Hemisphere: +1 239 945 6433 Eastern Hemisphere: +66 92 536 3380 🤍 | 🤍 | 🤍 | 🤍 Read More on the MyMLM Blog: 🤍 Hi. My name is Robert Proctor. For the last 20 years, I've been involved in the launch of over 1,000 network marketing companies. Today, only 10% of those companies are still in business. 90% failed. I want to give you some tips and tools, some hints and suggestions to look for when you're launching a network marketing company to be part of the 10% and avoid being part of that 90%. So, what is software versioning? This is a question when you're shopping for MLM Software you should be asking your software provider if they version their software. What does software versioning mean? Well, it means that Company A buys the MLM software and they get Version 1 of the software. It's got some certain features and benefits, some modules et cetera. Now Company B buys another version of the software. We'll call that Version 2. They've got some different features, functionality in the software. And now, Company 3, You, buys the software. You've got some different features, some different functionality in the software. When this MLM software company upgrades their software in a versioning software system, typically, they'll go back to Company A, put their hands out and ask for more money so that they can get the upgrade to the new version. Then they go to Company B and they ask for more money from Company B so they can get the upgrades to the new version because Company C has already got that. And they're generating additional revenue for their company by selling versioning. There are some bad habits that go along with that, too. Besides versioning their software, when there's a bug in the software, what happens when a new browser rolls out, a new denial of service or some sort of anti-virus rolls out, they've got to go back to Version 1 and update it. Go back to Version 2 and update it. Go back to Version 3 and all the versions of the software, and they've gotta update that software. It takes a long time. It means also, you're not getting the latest, greatest features and functionality in the software. This is why you should be looking for an MLM software application that's a cloud-based service application. When they upgrade their software, everybody is getting the upgrade. It's no longer versioned. It's what's called software as a service subscription services. you look at things like Adobe Photoshop and Microsoft Office, any time that Microsoft Office rolled out a new version, you had to buy that new version of the software. Anytime Adobe uploaded a new version or came up with a new version of Photoshop or any of their technologies, you had to pay for that new version. Nowadays, companies such as Microsoft and Adobe, they have what's called: subscription services. That's cloud-based subscription services that you never have to pay for upgrades again. So when you're looking for that MLM software provider, look to see that there are a cloud-based service subscription software, not a versioning software. If you got some value from this video, do me a favor: Like it. Share it. If you think some others would get some value from it, let them know about it. And hey, we'll see you on the next video. Have a great day! Western Hemisphere: +1 239 945 6433 Eastern Hemisphere: +66 92 536 3380 sales🤍 🤍 | 🤍 | 🤍 | 🤍

API Versioning Explained | Lightboard Series


Welcome to MuleSoft Training! Learn about your options for API Versioning. Versioning is one way to indicate that you are making a breaking change to your implementation. To learn more about this topic, check out this article: 🤍 Thanks for watching!

API Versioning Strategy


With all the work that goes into your API program, from strategy through operations, the last thing you want to do is create confusion for developers by making your API Versioning confusing or difficult to understand. Consistency will be critical to creating a lasting relationship with developers that want to use your APIs. API versions should be a key ingredient in your governance of your API program. So when should versioning happen? While the start versioning should not happen too often as this can be very impactful and may require developers to update their code. In many instances, implementing a new API version without thoughtful analysis and testing will result in broken software. And broken software can negatively impact the image of our developers and our company. Also, a new API version should be implemented when new required fields are introduced into the payload. Developers need to change their software and potentially collect new information or ensure previously optional data is now required. And a final example previous data has been removed. This may be either in the call where some parameters are no longer valid to pass into the API, or data was returned is no longer there. These may cause software problems or require the developer's attention. So creating and having a clear set of parameters know when a new version is required or not required will be an important decision for your organization. Let's talk about how companies consider options for API version naming. We'll show three examples but there is not one right answer. If you explore companies that publicly post their APIs for consumption, you'll quickly see there may be a preference towards a version naming practice, but it is not consistent from one company to the next. Therefore, your company needs to figure this out from the start and then stick to it. Consistency is critical. You'll hear this repeated several times in this video. In this example, the URI includes a date to distinguish the different API versions. New software or new developers would opt to then select the API with the most current date. This also gives them visibility into how often versions are released by looking back at older versions of the API. This isn't a guarantee though as companies would eventually deprecate older versions from the API portal and you would not have visibility into these. Our second example shows how you can set the version number into the custom header. This is convenient but it is not easy to explore with common tools. And our third example shows how the version indicator is placed into the URI. This makes it very clear for developers to know which version is the latest as the path needs to be compatible to process correctly. With each of these examples, there are pros and cons. Consider each carefully while deciding what your company will do for versioning. Of course, there will be disagreements and someone needs to be empowered to make a final decision. Still having issues deciding? Well, we recommend going with option three for embedding the version into the URI path. Please note that there are even disagreements within Apigee about API Versioning. Each engineer has a preference and may make a different recommendation. We see this option though as something as simple, unambiguous, and intuitive meaning is easily understandable, can be passed into testing tools and when a change happens, the URI changes. So you can see the domain is updated its resource model. So now let's turn our attention next to a critical piece in this whole process, communication. How do you ensure your developers are aware of new versions and show we have a transition period for developers to move versions. Creating a new API version with immediate requirement for all developers to use the new version will be a recipe for disaster unless, of course, your developer community is all internal developers or limited trusted partners that know this is how your company releases versions. So in most instances, you want to have a transition and your older versions will remain active and in use for a period of time. But how much time? Typically the rule of thumb is anywhere from 6-12 months. During this time, you'll still need to maintain these older versions or things like security patches or bugs that may arise. You may also have one key developer that requests a change and isn't in the immediate position to make a version update. Here are some things you need to consider in setting the deprecation date. How long is your API been available? How many developers are using your APIs? What is the traffic volumes of your API? All of these are more critical to analyze and make a decision on how long to maintain an older version. And it wouldn't be right for us not to end the video with one more mention of being consistent. Remember that the best API has high use across developers in many ways not previously thought.

What is Semantic Versioning?


Semantic versioning (🤍 is a specific way of structuring and using version numbers for APIs and other software artifacts. In this video we look at the details of how versions are numbered using a "MAJOR.MINOR.PATCH" pattern, and what that means in practice. Semantic versioning only makes sense when there is a well-defined model of backwards compatibility and how APIs and other software artifacts can evolve. This video is the first in a three-part series that discusses semantic versioning, how to manage API versioning, and how to design APIs for extensibility and evolvability. We also discuss "Hyrum's Law", which is an important consideration when it comes to using semantic versioning in practice. Hyrum's law tells us to be careful with backwards compatibility, because API consumers tend to rely on all observable behavior of an API, including some that may change. If you are interested in the four-part mini-series about API lifecycle management, here are links to all videos in that series: 1. "What is Semantic Versioning" 🤍 (this video) 2. "Managing API Versions: The API Lifecycle" 🤍 3. "Designing APIs for Extensibility: How to create evolvable APIs" 🤍 4. "API Lifecycle Management: Deprecation and Sunsetting" 🤍

Versioning ASP.NET Core Services


Phil Japikse shares a number of tips on how to manage multiple versions of ASP.NET Core Services. How do you and the API consumers easily keep track of versions 1.0, 1.1, 1.2, 2.0 etc? Phil shows how.

Understanding Semantic Versioning with Real World Examples


Semantic Versioning, or semver for short, is one of those systems that's used all the time by JavaScript or Ruby developers (and others) but often not understood. It's one of those systems that just sorta works and you don't have to think about it too much, but it actually helps a lot to take some time and understand what the numbers mean and the implications of updating to a new version. In this video, I'm going to show some really popular packages being used and updated as a sort of real world example, while still keeping the code itself simple. I'm hoping by doing this you can get a hands on example of what it means to update each version number (Major, Minor, and Patch) and how to troubleshoot breaking changes. Knowing this just gives you a lot more control over your project dependencies, and I think it makes you a better software developer if the ideas are new. Code Repositories for reference: 🤍 🤍 NPM Semantic Versioning video: 🤍 Old package lockfile video: 🤍 ~~~~~~ 00:00 - What we'll cover 01:05 - Explanation of Semantic Versioning 07:48 - Quick project setup and npm commands 15:17 - Minor update example (inquirer) 19:15 - Patch update examples (inquirer) 20:36 - Tilde (~) character example (inquirer) 22:29 - How to see versions of a package 24:06 - Major (breaking change) example (inquirer) 29:44 - Chalk package and a Major update fix example 38:33 - Thinking in a semver mindset ~~~~~~ Follow Jimmy Cleveland's doings: twitter: 🤍 blog: 🤍 #javascript #npm #semver

NPM - Efficient Project Versioning


This brief tutorial explains how you can manage the version numbers of your projects through the package.json file, on the command line, or through build scripts with the npm version command.



Implementing versioning | ASP.NET Core 5 REST API Tutorial 2


Become a Patreon and get source code access: 🤍 Check out my courses: 🤍 Hello everybody I'm Nick and in this video we will talk about the importance of versioning in our API and how we can implement it. Don't forget to comment, like and subscribe :) Social media: Follow me on GitHub: 🤍 Follow me on Twitter: 🤍 Connect on LinkedIn: 🤍 #tutorial #rest #api

Versioning strategy for a complex internal API


This is a session given by Konstantin Yakushev at Nordic APIs 2016 Platform Summit on October 25th, in Stockholm Sweden. Description: API versioning is a very heated topic in API design world. Common approaches are passing version number explicitly (with a lot of fairly useless discussion on where exactly to put that number) or only introducing backwards-compatible changes. When creating internal API for Badoo applications we found those approaches to be too limiting. Passing version number requires implementers to accommodate for all breaking changes when bumping version – even when it’s not required for business goals of that application at the time. Instead of driving value for business, application developers are in constant race to keep up with the API. Never introducing incompatible changes is also not an option. After several feature redesigns (something that may happen at Badoo once every few weeks) protocol becomes bloated and half of the fields transmitted over the wire start being useless. This talk is about our approach to versioning as part of client-server component negotiation. Client announces features and capabilities it supports and server replies with features status: whether they are enabled or disabled and whether they can be enabled by some user action (e. g. by buying some paid product). Beside those componentized features, client also sends support flags such as SUPPORT_IMAGE_SIZE_VIA_URL which affects how API works. We use those flags where in typical API a version number bump would be required. This approach allows both server and client to understand their current state and adjust their code accordingly – essentially, a tailor-made API for every client. Gathering data on feature and flag support among clients allows us to remove old code branches while continuing to evolve the API. As a result, we are not afraid to change something when that change is required. Old clients continue to work while protocol rot is kept at low level. In this talk I will give details on how exactly this versioning scheme work, how we test those changes, how and when we deprecate our old clients and note some stats and insights from using this scheme at Badoo for several years. Learn more at 🤍

Easiest tutorial on Versioning in the document library of SharePoint Online


learn how to use Versioning in the document library of sharepoint online. This is a very basic and very quick tutorial.

Lesson 41 - Microservices Contract Versioning


In this lesson Mark Richards discusses versioning within a microservices ecosystem and shows why and how to do contract-level versioning within microservices. Stay tuned each Monday for more lessons in Software Architecture at 🤍

The 3 Categories of Data Versioning


What exactly is data versioning? Einat Orr, CEO and Co-Founder of Treeverse, is here to explain for us by breaking it down into three categories. Watch the full episode here: 🤍 Subscribe to the Podcast ►►🤍 Join the Dev Interrupted Community ►►🤍 View more Podcast Highlights ►►🤍 Find out more about Dev Interrupted on our website ►► 🤍 Join us at INTERACT on October 25, 2022! Register here: 🤍

Versioning APIs with ASP NET Core


Announcing .NET Core 3.0: 🤍 Building an API with ASP.NET MVC in .NET Core is only half the job. If your API is going to live more than one release cycle, you are going to need to version it. In this talk by Shawn Wildermuth, we'll show you how easy it is now to version APIs using functionality built into ASP.NET Core.

Automated Build Versioning with Github Actions and Conventional Commits by Roman Ivaniuk


We are going to try and cover the topic of Conventional Commits, how it benefits the process of development, and how we can then automate some of the CI&CD steps in a project using Github Actions. Intro to Semantic Versioning Intro to Conventional Commits What we can automate with Conventional Commits Intro to Github Actions Practical example Next steps, conclusion

Temporal Tables for Row Versioning with Transact-SQL (part 1)


In this video I'm demonstrating how you can create a SQL Server table in such a way that you get automatic vesioning of rows, using Temporal Tables/System Versioning

Web API Versioning | Additive Change Strategy


Change management is crucial in building and maintaining successful Web APIs. In this video, I go through one possible approach to API versioning using a strategy called additive-change strategy. Timecodes 0:00 - Intro 0:38 - Why version APIs? 3:05 - Additive-change strategy 6:14 - Caveats 7:08 - Conclusion

API Versioning with NestJS 8 Tutorial


In this API tutorial with NestJS (NodeJS framework) we take a look at utilizing the n ew API Versioning feature which recently got introduced to Nest 8. We cover exactly how to get started, how to document different versions with swagger, as well as several different strategies to accomplish the task!

Rest api versioning | api versioning | api versioning demo | api versioning code example | okayjava


rest api versioning | api versioning | api versioning demo | api versioning code example | okayjava Buy me a coffee - 🤍 01 - What is api versioning? 02 - Breaking v/s Non breaking api changes 03 - Types of API Versioning 04 - Live code… URI VERSIONING : This strategy involves putting the version number in the path of the URI, and is often done with the prefix "v". 🤍 🤍 REQUEST PARAMS : This type of versioning adds a query param to the request that indicates the version. 🤍 🤍 VERSIONING USING CUSTOM REQUEST HEADER : A custom header allows us to preserve api URLs. Version information is specified in the Request Header without the need for any change in the URL. 🤍 headers=[X-API-VERSION=1] VERSIONING USING ACCEPT HEADER : Accept header define the media type and character encodings. We can also pass version information for Web API through accept headers without changing the URL. It is also known as media type versioning or content negotiation or accept header. i.e. 🤍 Accept: application/vnd.demo.v1+json source code - 🤍 PLEASE SUBSCRIBE FOR MORE VIDOES :)

#17: Semantic Versioning with package.json - Mastering NPM


Don't forget to subscribe and like the video if you enjoyed :) Be a damner, join the coding community: 🤍

Semantic Versioning with NPM


You've probably noticed that software version numbers have three digits separated with periods. Each number has a specific meaning. When installing packages with Yarn or NPM you need to understand the syntax that you can use to restrict or allow different versions by npm. NPM server calculator: 🤍 SemVer website: 🤍 NPM semver reference page: 🤍

Data Versioning and Reproducible ML with DVC and MLflow


Machine Learning development involves comparing models and storing the artifacts they produced. We often compare several algorithms to select the most efficient ones. We assess different hyper-parameters to fine-tune the model. Git helps us store multiple versions of our code. Additionally, we need to keep track of the datasets we are using. This is important not only for audit purposes but also for assessing the performances of the models, developed at a later time. Git is a standard code versioning tool in software development. It can be used to store your datasets but it does not offer an optimal solution. An alternative solution is to use Data Version Control (DVC). Despite its name, it is not just a data versioning tool, but also enables model and pipeline tracking. It runs on top of Git, which makes it easy to learn for Git users. At the same time, it overcomes the limitations of storing big files by storing them remotely (e.g. Azure, S3) and keeping in Git only their metadata. MLflow is a tool that is easily integrated with the code of your model and can track dependencies, model parameters, metrics, and artifacts. Every run is linked with its corresponding Git commit. Once the model is trained, MLflow can pack it in different flavors (e.g. Python/R function, H2O, Spark, TensorFlow…) ready to be deployed. DVC also runs along with Git. When MLflow helps you manage Machine Learning lifecycle, DVC helps you manage your datasets. In this tutorial, we will learn how to leverage the capabilities of these powerful tools. We will go through a toy ML project and look at the sample code on how to increase the reproducibility of individual steps. About: Databricks provides a unified data analytics platform, powered by Apache Spark™, that accelerates innovation by unifying data science, engineering and business. Read more here: 🤍 See all the previous Summit sessions: 🤍 Connect with us: Website: 🤍 Facebook: 🤍 Twitter: 🤍 LinkedIn: 🤍 Instagram: 🤍 Databricks is proud to announce that Gartner has named us a Leader in both the 2021 Magic Quadrant for Cloud Database Management Systems and the 2021 Magic Quadrant for Data Science and Machine Learning Platforms. Download the reports here. 🤍

Tutoriel git : Comprendre le versioning


Article ► 🤍 Abonnez-vous ► 🤍 Dans ce tutoriel vidéo vous verrez l'intérêt de l'utilisation d'un système de versioning dans le cadre d'un travail en équipe. Ce tutoriel ne propose qu'une approche théorique, une autre vidéo concernant l'utilisation d'un tel système (git avec github) sera disponible prochainement Soutenez Grafikart: Devenez premium ► 🤍 Donnez via Utip ► 🤍 Retrouvez Grafikart sur: Le site ► 🤍 Twitter ► 🤍 Discord ► 🤍



#semver #versioning #githubactions How do you version your projects? Are you doing it manually? Well, let's automate it all on Github Actions with GitVersion. Links: Codebase - 🤍 SemVer - 🤍 GitFlow by Atlassian - 🤍 Always excited to hear your suggestions about topics you are interested in! Twitter: 🤍

Versioning and Exporting Components in Bit


Once you have built your component you can then version it using `bit tag` and then export it using `bit export`. You will then see your component on and you can copy the package name and use it in another component or any other app.

Using object versioning


Ever wondered how you can use the Object Versioning feature on Cloud Storage? In this episode of Getting Started with Google Cloud Platform, we’ll show you how to use this feature, and we’ll also demo the different ways you can work versioned objects in Cloud Storage. Watch to learn more about versioned objects! Timestamps: 0:00 - Intro 0:27 - Enable Versioning For A Cloud Bucket 0:48 - Stop Versioning For A Cloud Bucket 0:57 - See If Versioning Is Enabled For A Cloud Bucket 1:30 - See All Versions That Have Existed Watch the Get Started with Google Cloud Playlist → 🤍 Subscribe to the GCP Channel for more content → 🤍 #GetStartedWithGoogleCloud Product: Cloud Storage; fullname: Bukola Ayodele;

Spring Boot REST API and versioning


Enjoy! :-) Thank you for commenting and asking questions. Library sign up referral link: 🤍 Get 25 % discount on your Minecraft servers at by using this referral link: 🤍 Checkout or buy the Introduction to Algorithms book at Amazon: 🤍 The code is located here: 🤍 Follow me on twitter: 🤍 Support me on Patreon: 🤍 As an Amazon Associate I earn from qualifying purchases. Check out the stuff that I like (always updated): 🤍

code.talks commerce 2019 - Versioning in a Microservice Architecture


by Stephan Schulze A microservice architecture can bring a lot of pain, when it comes to versioning of services, APIs and Frontends. Unfortunately you can not really go without it, at least if you want to be with a stable system. This talk is based on a real world implementation, that covers everything from Services to Frontend to API to Document Format Versioning.

56. Semantic Versioning for a Software. Understanding major, minor & Patch release in Version - GIT


In this video, we will see what is semantic versioning. How to give a version for software that is major, minor, and patch release in GIT. If you like my video, please subscribe to my channel. My Playlists: React Complete Course: 🤍 Vue Complete Course: 🤍 Angular NGRX Complete Course: 🤍 Angular Complete Course: 🤍 TypeScript Complete Course: 🤍 ES6 Complete Course: 🤍 Javascript Complete Course: 🤍 GIT Complete Course: 🤍 My Courses Playlist Page: 🤍 Youtube Page: 🤍 Twitter Page: 🤍 Linkedin: 🤍 GitHub: 🤍 #GIT #leelawebdev Join this channel to get access to perks: 🤍

Package Versioning - Best Practices with Semantic Versioning (SemVer)


To access the full training seminar, go to 🤍 To request on-site or remote training for your team, for any of Inedo’s products, go to 🤍 Software packaging is immensely useful for deployment of software libraries, tooling, and more. There is a package system for almost every environment you could imagine. But how does this help you with environments that don't share a common packaging system? Our solution is to build Universal Packages that allow you to take your software wherever it is you need it to go. Download the UPack: 🤍 Download the free version of ProGet: 🤍

Git for Data Lakes—How lakeFS Scales Data Versioning to Billions of Objects


Modern data lake architectures rely on object storage as the single source of truth. We use them to store an increasing amount of data, which is increasingly complex and interconnected. While scalable, these object stores provide little safety guarantees: lacking semantics that allow atomicity, rollbacks, and reproducibility capabilities needed for data quality and resiliency. lakeFS - an open source data version control system designed for Data Lakes solves these problems by introducing concepts borrowed from Git: branching, committing, merging and rolling back changes to data. In this talk you'll learn about the challenges with using object storage for data lakes and how lakeFS enables you to solve them. By the end of the session you’ll understand how lakeFS scales its Git-like data model to petabytes of data, across billions of objects - without affecting throughput or performance. We will also demo branching, writing data using Spark and merging it on a billion-object repository. Connect with us: Website: 🤍 Facebook: 🤍 Twitter: 🤍 LinkedIn: 🤍 Instagram: 🤍

REST API - Versioning Demo


REST API - Versioning Demo watch more videos at 🤍 Lecture By: Mr. Ravikiran S, Tutorials Point India Private Limited

AWS S3 Object Versioning and Lifecycle Rules


Hello in this video I will explain how to enable versioning in your S3 bucket and how it works in terms of having multiple versions of the object in the bucket and what a "delete marker" is. I will also show how to use lifecycle rules with versioning to change the storage class of your object Study Material: ACloudGuru Course: [🤍 WhizLabs: [🤍 00:00 Intro 00:41 Enable Bucket Versioning 01:22 Enable public access 03:28 Object versioning example 04:25 Delete Marker 05:08 Versioning Properties 05:40 Lifecycle Rules If you want to learn more about AWS Services, make sure to subscribe to the channel: Youtube 🎥 - 🤍 Medium: 🤍 🌎 Find me here: Twitter - 🤍

Что ищут прямо сейчас на
versioning Parlimen casa com jardim дорога из варшавы в норвегию columbæ تلك الايام dinero Биткоин прогноз winrar sinhala russian dialogue advanced журналист Kopi торговля на новостях prikolvideolar Param Joshi Norse racecar paradesi review прослушка Nisar Khuhro