Day 70: A Read-Only User and a Template

Day 70 of DevOps, Day 20 of Azure. Both tasks today were about what a system does to the things you did not mention. In Jenkins, a permission you do not tick is denied, which is the easy half. In ARM, a property you leave out of a template is reset to its default on the next deployment, which is not what the word incremental led me to expect. One Jenkins task, one Azure task. Create a user and give them read-only access, then edit and deploy an ARM template. The tasks come from the KodeKloud Engineer platform. Task 1: A read-only Jenkins user The task: create kirsty with full name Kirsty and password BruCStnMT5, then grant read-only access using a project-based matrix authorisation strategy. Step 1: Create the user Manage Jenkins, Users, Create User, with the three values the task gave. That part is a form. Step 2: Install the strategy, because it is not in Jenkins This is the step the task's wording assumes you will work out. Matrix Authorisation S