Skip to content
This repository has been archived by the owner on May 6, 2020. It is now read-only.

aws,packet: make tags more uniform #179

Merged
merged 1 commit into from
Feb 17, 2020
Merged

aws,packet: make tags more uniform #179

merged 1 commit into from
Feb 17, 2020

Conversation

alban
Copy link
Contributor

@alban alban commented Feb 13, 2020

On Packet, tags are a list of strings.
On AWS, tags are a key-value map.

There are some default tags:

  • ManagedBy = Lokomotive
  • CreatedBy = Unspecified

and some suggestions:

  • ManagedBy = Lokomotive
  • CreatedBy = DevOpsTeam

Related:

@@ -316,6 +316,7 @@ Lokomotive implements support for some [DNS providers](../dns/), if your provide
| reservation_ids_default | Default hardware reservation ID for nodes not listed in the `reservation_ids` map. | "" | "next-available"|
| certs_validity_period_hours | Validity of all the certificates in hours | 8760 | 17520 |
| controller_clc_snippets [[1]](#clc-snippets-limitation) | Controller Container Linux Config snippets | [] | [example](../advanced/customization.md#usage) |
| tags | Optional details to tag on Packet resources | `[]` | `["CreatedBy-DevOpsTeam"]` |
Copy link
Contributor

@johananl johananl Feb 13, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest we use : as a separator between the "key" and the "value" in Packet tags. The hyphen is less clear semantically IMO. Additionally, hyphens are much more likely to exist as part of either the key or the value, which would make it hard to know where the key ends and the value begins.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated.

Copy link
Contributor

@invidian invidian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems like a duplicate of #170.

@@ -223,7 +223,7 @@ Reference the DNS zone id with `"${aws_route53_zone.zone-for-clusters.zone_id}"`
| service_cidr | CIDR IPv4 range to assign to Kubernetes services | "10.3.0.0/16" | "10.3.0.0/24" |
| cluster_domain_suffix | FQDN suffix for Kubernetes services answered by coredns. | "cluster.local" | "k8s.example.com" |
| certs_validity_period_hours | Validity of all the certificates in hours | 8760 | 17520 |
| tags | Optional details to tag on AWS resources | `{}` | `{"CreatedBy" = "Devops team"}` |
| tags | Optional details to tag on AWS resources | `{}` | `{"CreatedBy" = "DevOps team"}` |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That seem unrelated to this PR/commit.

@invidian
Copy link
Contributor

#170 has been merged, so this PR needs to be rebased.

On Packet, tags are a list of strings.
On AWS, tags are a key-value map.

There are some default tags:
- ManagedBy = Lokomotive
- CreatedBy = Unspecified

and some suggestions:
- ManagedBy = Lokomotive
- CreatedBy = DevOpsTeam
@alban alban changed the title packet: add tags on packet resources aws,packet: make tags more uniform Feb 17, 2020
Copy link
Contributor

@invidian invidian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks OK.

@alban alban merged commit ac71066 into master Feb 17, 2020
@invidian invidian deleted the alban/tags-2 branch February 17, 2020 14:59
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants