IAM Level 100 - Part 5: Tags and Tag Namespaces

Просмотров 12 тыс.

% 82

Introduction to Tags and Tag Namespaces
Learn More: www.oracle.com/cloud/iaas/training/
Register for a free live webcast: www.oracle.com/cloud/iaas/training/register-for-training.html
=================================
To improve the video quality, click the gear icon and set the Quality to
1080p/720p HD.
For more information, see www.oracle.com/goto/oll and docs.oracle.com
Copyright © 2019 Oracle and/or its affiliates. Oracle is a registered trademark of Oracle and/or its affiliates. All rights reserved. Other names may be registered trademarks of their respective owners. Oracle disclaims any warranties or representations as to the accuracy or completeness of this recording, demonstration, and/or written materials (the “Materials”). The Materials are provided “as is” without any warranty of any kind, either express or implied, including without limitation warranties or merchantability, fitness for a particular purpose, and non-infringement.

Наука

Опубликовано:

18 ноя 2019

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 4

@shukrilius 4 года назад

Hi Rohit! All the videos were so useful!!! Thanks for your time.

@TheJohnnySilver 3 года назад

However, there is one mismatch in this video. You have applied advanced tag (${iam.principal.name}) to the free-form tags, which eventually will not work (i.e. mangled to user identity). Please correct me if I'm wrong.

@TheJohnnySilver 3 года назад

I'm wondering, what would be the way to enforce Tags Namespaces for individual Compartments? Lets say, in one Tenant I have multiple teams, each team has its own dedicated Compartment (plus policy to restrain neighbor Compartments), each Compartment must have a set of mandatory tags set (e.g. TeamName, TeamContact, CostCenter, etc.), and no one will be able to provision cloud resources without these tags set.

@MaheshPatil-rh4lt 3 года назад

Thanks for video.. Can we do tag restriction to all the resources in compartment? Let say i created tag namespace (operations) under that defined 4 key parameters.. if user do not mention those 4 key parameter to the resources then resource will not run. it will restrict to run the resources/services. Can we do this?