Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Specify key formats and values

You can restrict users to a set of key formats and values.

This tag policy specifies:

  • Tag key format must be “CostCenter” or “Costcenter”

  • Tag values must be “Production” or “Test”

  • Users creating child policies cannot do any operations

All key format capitalizations are allowed

You can allow users to capitalize tag keys as they prefer, or at least ensure they don't have to worry about åccidentally leaving the caps lock on! 

This tag policy specifies:

  • Tag key format is “costcenter” but ignore case

  • Tag values must be “Production” or “Test”

  • Users creating child policies cannot do any operations

All values are allowed

You can allow users to enter any value for a specific tag key. 

This tag policy specifies:

  • Tag key format must be “CostCenter”

  • All tag values are allowed

  • Users creating child policies cannot do any operations

Tag to flag a resource

A tag with a key only can be useful to mark a resource or group of resources.

This tag policy specifies:

  • Tag key format must be “upgradeOS”

  • Tag values must be empty (don't enter a value, just click Add)

  • Users creating child policies cannot do any operations

Ban use of a key

You can prevent users from creating a tag with a specific key.

This tag policy specifies:

  • Any tag keys equal to “costcenter” (ignore case) are not allowed

  • Any tag value is allowed

  • Users creating child policies cannot do any operations

Ban use of a concrete key format

You can enter a specific key format to prevent users from creating tags with these keys and values.

This tag policy specifies:

  • Tag key format "CostCenter" cannot be used

  • Any tag value is allowed

  • Users creating child policies cannot do any operations

Ban use of a concrete key format and values

You can enter specific key formats and values to prevent users from creating tags with these keys and values.

This tag policy specifies:

  • Prohibit the use of tag key format “CostCode” with value “GEN13”

  • Users creating child policies cannot do any operations

Allow inheritors to append

If the tag policy will allow inheritors to append, users creating child tag policies can add tag formats and values.

Allow inheritors to remove

If the tag policy will allow inheritors to remove, users creating child tag policies can remove tag formats and values.

Edit resource tags with allow tag policy

When the user enters a Key or Value, the UI lists allowed formats and values.

If the user enters invalid tags, the platform will mark them in the Compliance report

Edit resource tags with deny tag policy

When the user enters a Key or Value, the UI lists banned formats and values.

 If the user enters invalid tags, the platform will mark them in the Compliance report

  • No labels