added labels migration #11707
added labels migration #11707
Conversation
joeyouss
requested review from
josephdlopez,
karanshetty53,
rajarshee-harness,
jyotiarora-harness and
richardblack-Harness
as code owners
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://68e637eba59cf25f10ac730f--harness-developer.netlify.app |
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://68e683946d1e750086206f43--harness-developer.netlify.app |
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://68e685eef8617f46fc7cab58--harness-developer.netlify.app |
|
|
||
| 1. Change the `identifier` from `LABEL` to `LABEL_V2` | ||
| 2. Change the `identifierName` from `Label` to `Label V2` | ||
| 3. Remove any prefixes (like `user_` or `aws_`) from your tag keys |
There was a problem hiding this comment.
Identify all the AWS labels (starts with user_ or aws_) and replace them with actual tag key. You don't have to update your other cloud provider labels. For other cloud providers, just do first two steps.
| { | ||
| field": { | ||
| "fieldId": "labels.value", | ||
| "fieldName": "key1", |
| "fieldId": "labels.user_key1", | ||
| "fieldName": "", | ||
| "identifier": "LABEL", | ||
| "identifierName": "Label V2" |
| ```json | ||
| "idFilter": { | ||
| "field": { | ||
| "fieldId": "labels.user_key1", |
| ```json | ||
| "idFilter": { | ||
| "field": { | ||
| "fieldId": "labels.key1", |
| "fieldId": "labels.key", | ||
| "fieldName": "", | ||
| "identifier": "LABEL", | ||
| "identifierName": "Label V2" |
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description
PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged: