codecommit: tag-resource does not permit `:` character in tag key

[mifisignal]

The following command incorrectly returns an error even though colon characters (:) in tag keys are legal:

aws codecommit tag-resource --resource-arn <arn> --tags namespace:KeyName=value

Expected behavior: a new tag is applied to the resource with the name namespace:KeyName and value value.

Actual behavior:

Error parsing parameter '--tags': Expected: '=', received: ':' for input:
namespace:KeyName=value

[justnance]

@otterley - Thanks for posting this issue. Try the following syntax:

aws codecommit tag-resource --resource-arn <arn> --tags Key=namespace:KeyName,Value=value

There are some other examples of tagging resources under the EC2 reference page.

Let us know if this helps.

[mifisignal]

Hi @justnance! Codecommit's tagging API is different from EC2's, and so the Key=k,Value=v syntax is not used by the tag-resource subcommand or its corresponding API. See the CLI documentation and API documentation for additional details.

Using the syntax above, you would instead get two tags: one called Key whose value is namespace:Keyname and another called Value whose value is value.

[justnance]

@otterley - Thanks for the feedback and sorry about recommending the wrong syntax. I reproduced and used the following:

aws codecommit tag-resource --resource-arn arn:aws:codecommit:us-west-2:123456789101112:clitags --tags name="namespace:KeyName",Value=Value5

aws codecommit list-tags-for-resource --resource-arn arn:aws:codecommit:us-west-2:123456789101112:clitags

{
    "tags": {
        "Value": "Value5",
        "name": "namespace:KeyName",
    }
}

I also found an example here but I looks like some of our other documentation could use some better examples. I'm going to get this escalated internally.

[no-response]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

[justnance]

@otterley - As discussed offline, I am reopening this issue as I was able to reproduce and confirm this issue with the following steps:

1. Created a new tag using the AWS Management Console which includes a colon and then listed it with the CLI:

$ aws codecommit list-tags-for-resource --resource-arn arn:aws:codecommit:us-west-2:1234567890101112:clitagtest
{
    "tags": {
        "namespace:Keyname": "namespaceValue"
    }
}

This confirmed the service was allowing a tag name with a colon. Next, I tried to create another new tag with a colon using the following the CLI command but it returned the same error reported in your first response:

$ aws codecommit list-tags-for-resource --resource-arn arn:aws:codecommit:us-west-2:1234567890101112:clitagtest
{
    "tags": {
        "namespace:Keyname": "namespaceValue"
    }
}

$ aws codecommit tag-resource --resource-arn arn:aws:codecommit:us-west-2:123456789101112:clitagtest --tags "namespace:KeyName2"=KeyNameValue

Error parsing parameter '--tags': Expected: '=', received: ':' for input:
namespace:KeyName2=KeyNameValue

I am escalating this internally and we are looking to get it resolved.

[no-response]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.